From fba6be7c420bd7d62b9bd20bcf2d7fe7e83994ba Mon Sep 17 00:00:00 2001
From: Kohsuke Kawaguchi <kk@kohsuke.org>
Date: Wed, 6 Mar 2013 08:54:30 -0800
Subject: [PATCH] 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.
---
 core/pom.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/core/pom.xml b/core/pom.xml
index 5edf04b16c..3fcb04b90b 100644
--- a/core/pom.xml
+++ b/core/pom.xml
@@ -42,7 +42,7 @@ THE SOFTWARE.
 
   <properties>
     <staplerFork>true</staplerFork>
-    <stapler.version>1.204</stapler.version>
+    <stapler.version>1.205</stapler.version>
     <spring.version>2.5.6.SEC03</spring.version>
   </properties>
 
-- 
GitLab