@daspilker: i can confirm, that @KrystianMarek is right. The cause is the transitive dependency in jenkins-test-harness. I you look at the pom of jenkins-test-harness:2.0 it contains the classifier war-for-test which seems to cause the problem even though the jpi-plugin does not have a direct dependency to the war-for-test anymore. Increasing the version to 2.31 for coreVersions > 2.63 will do the trick.
{noformat} @daspilker: i can confirm, that @KrystianMarek is right. The cause is the transitive dependency in jenkins-test-harness. I you look at the pom ofjenkins-test-harness:2.0it contains the classifier war-for-test which seems to cause the problem even though the jpi-plugin does not have a direct dependency to the war-for-test anymore. Increasing the version to 2.31 for coreVersions > 2.63 will do the trick.{noformat}