Branch: refs/heads/master
Home: https://github.com/jenkinsci/jenkins
Commit: 9514fb1a9fc938226da320e68afb3623cba3dfe9
https://github.com/jenkinsci/jenkins/commit/9514fb1a9fc938226da320e68afb3623cba3dfe9
Author: Kohsuke Kawaguchi <[email protected]>
Date: 2013-03-06 (Wed, 06 Mar 2013)
Changed paths:
M test/src/test/java/lib/form/RepeatableTest.java
Log Message:
-----------
fixed the test regression caused by json-lib 2.4
Commit: fba6be7c420bd7d62b9bd20bcf2d7fe7e83994ba
https://github.com/jenkinsci/jenkins/commit/fba6be7c420bd7d62b9bd20bcf2d7fe7e83994ba
Author: Kohsuke Kawaguchi <[email protected]>
Date: 2013-03-06 (Wed, 06 Mar 2013)
Changed paths:
M core/pom.xml
Log Message:
-----------
Fixing a test regression.
See 010b47d7307a11f0750fc01a00d99b96bbab9234 in stapler/stapler for the
actual fix.
I first discovered this on my local desktop yesterday as I was verifying
the fix for json-lib 2.4. From what I can tell, this has been broken all
along and it was working only because Facets are discovered in the lucky
order; JellyFacet got a chance to get at it before GroovyFacet did.
When I rebuilt from clean the problem stopped appearing, so I assumed
that there are some factors that cause JellyFacet to get loaded before
GroovyFacet (maybe the order in which Maven iterates dependencies or
something like that.)
But I'm no longer so sure now that I know J-on-J saw this problem at
about the same time. That's just too many coincidences.
But let's see if this would make J-on-J happy.
Compare:
https://github.com/jenkinsci/jenkins/compare/938a5802ae53...fba6be7c420b
--
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
