Code changed in jenkins
User: Jesse Glick
Path:
changelog.html
test/src/main/java/org/jvnet/hudson/test/HudsonTestCase.java
test/src/main/java/org/jvnet/hudson/test/JenkinsRule.java
http://jenkins-ci.org/commit/jenkins/31c302cc7e4a63727f7684eef3cf6ce5bc7aa12d
Log:
[FIXED JENKINS-18918] From plugins we must use target/ not target/classes/ to unpack Maven.
Also cleaning up variable names to be less misleading.
Note that new File("target") is really a bad idea since we cannot predict the CWD in effect when Maven is run.
(From the standard bin/mvn launcher, it seems that it will always be some Maven project at least.
This may not be true for Maven run embedded from various tools.)
But leaving that as is for now, since it is not clear how else we would find the project location.
(new File(env.description().getTestClass().getProtectionDomain().getCodeSource().getLocation().toURI()).getParentFile() might work but it is pretty hacky.)
(cherry picked from commit 2152cf478e26e01b90be8c818cfe3bb628b32263)
Code changed in jenkins
User: Jesse Glick
Path:
changelog.html
test/src/main/java/org/jvnet/hudson/test/HudsonTestCase.java
test/src/main/java/org/jvnet/hudson/test/JenkinsRule.java
http://jenkins-ci.org/commit/jenkins/2152cf478e26e01b90be8c818cfe3bb628b32263
Log:
[FIXED JENKINS-18918] From plugins we must use target/ not target/classes/ to unpack Maven.
Also cleaning up variable names to be less misleading.
Note that new File("target") is really a bad idea since we cannot predict the CWD in effect when Maven is run.
(From the standard bin/mvn launcher, it seems that it will always be some Maven project at least.
This may not be true for Maven run embedded from various tools.)
But leaving that as is for now, since it is not clear how else we would find the project location.
(new File(env.description().getTestClass().getProtectionDomain().getCodeSource().getLocation().toURI()).getParentFile() might work but it is pretty hacky.)
Compare: https://github.com/jenkinsci/jenkins/compare/11953750ab42...2152cf478e26