>>>>> On Fri, 19 Aug 2011 10:47:02 -0400, Cheng Fang <cheng.fang_at_oracle.com> said:
CF> Any difference (version, etc) between bean-validator.jar in 3.1.2 and
CF> trunk? Their size is different:
CF> in 3.1.2: 1164011 Aug 19 10:33 bean-validator.jar
CF> in trunk: 387450 Aug 19 10:32 bean-validator.jar.trunk
CF> When running tests devtests/ejb/ejb31/embedded/embedasync with a locally
CF> built 3.1.2 glassfish, this test failed with slf4j errors. But if I
CF> replace bean-validator.jar with trunk's version, it passed. The errors
CF> when it failed:
CF> [java] SEVERE: Exception while loading the app
CF> [java] Aug 19, 2011 10:41:28 AM
CF> org.glassfish.deployment.admin.DeployCommand execute
CF> [java] SEVERE: Exception while loading the app :
CF> org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V
CF> [java] Aug 19, 2011 10:41:28 AM
CF> org.glassfish.ejb.embedded.EJBContainerProviderImpl createEJBContainer
CF> [java] INFO: [EJBContainerProviderImpl] Cleaning up on failure ...
CF> I suspect it's caused by version conflict of slf4j bundled in
CF> bean-validator.jar and weld-osgi-bundle.jar (both jars contain slf4j
CF> classes). It seems this conflict was introduced into 3.1.2 (not sure
CF> about 3.1.1), but not in trunk.
CF> Could someone confirm it?
Yes, I have seen this too. It is currently impacting the TCK team and
Kyle Grucci is looking after it.
I have BCc'd him on this message, as I don't know if he follows this list.
Ed
--
| edward.burns_at_oracle.com | office: +1 407 458 0017
| homepage: | http://ridingthecrest.com/
| 21 business days until JSF 2.2 Early Draft Review
| 25 business days until JavaOne 2011