Branch: refs/heads/master
Home: https://github.com/jenkinsci/jenkins
Commit: 68f1fa281f49a8bf7508ec33449887229932ed4e
https://github.com/jenkinsci/jenkins/commit/68f1fa281f49a8bf7508ec33449887229932ed4e
Author: Jesse Glick <jgl...@cloudbees.com>
Date: 2013-07-24 (Wed, 24 Jul 2013)
Changed paths:
M test/src/main/java/org/jvnet/hudson/test/WarExploder.java
Log Message:
-----------
Comment about probable bug.
Commit: 2152cf478e26e01b90be8c818cfe3bb628b32263
https://github.com/jenkinsci/jenkins/commit/2152cf478e26e01b90be8c818cfe3bb628b32263
Author: Jesse Glick <jgl...@cloudbees.com>
Date: 2013-07-24 (Wed, 24 Jul 2013)
Changed paths:
M changelog.html
M test/src/main/java/org/jvnet/hudson/test/HudsonTestCase.java
M test/src/main/java/org/jvnet/hudson/test/JenkinsRule.java
Log Message:
-----------
[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
--
You received this message because you are subscribed to the Google Groups
"Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-commits+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
