-
Bug
-
Resolution: Done
-
Critical
-
EAP_EWP 5.1.1, EAP_EWP 5.1.2
-
None
-
Not Required
-
NEW
Just noticed that running tests while patching jbosscache-core.jar (one-off release) the springdeployer test uses the incorrect jar in the integration testsuite. Here are the sums of the files after running a TS
rhusar@jawa26:jboss-5.1.1/ md5sum `find . -name jbosscache-core.jar` ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/cluster-udp-BR-1/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/cluster-udp-1/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/cluster-tcp-0/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/jbossmessaging/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/cluster-ustxsticky-0/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/bootstrapdependenciesJBAS5349-EJB3Message/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/cluster-profilesvc-0/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/bootstrapdependenciesJBAS5349-EJB3Entity/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/binding-manager2/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/tomcat-sso-cluster0/lib/jbosscache-core.jar faa2c964de0f06a7d0beb24cc58424ac ./server/springdeployer/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/jts/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/tomcat-sso-cluster1/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/binding-manager1/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/cluster-profilesvc-1/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/bootstrapdependenciesJBAS5349-datasource/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/cluster-tcp-SYNC-0/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/web/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/cluster-tcp-BR-1/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/cluster-ustxsticky-1/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/cluster-tcp-SYNC-1/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/all/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/cluster-udp-SYNC-1/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/cluster-tcp-1/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/cluster-udp-0/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/bootstrapdependenciesJBAS5349-EJB2Session/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/bootstrapdependenciesJBAS5349-EJB3Session/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/bootstrapdependenciesJBAS5349-EJB2Message/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/bootstrapdependenciesJBAS5349-RAR/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/cluster-udp-BR-0/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/cluster-tcp-BR-0/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/production/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/cluster-udp-SYNC-0/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/bootstrapdependenciesJBAS5349-WAR/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/scoped-aop-jdk50/lib/jbosscache-core.jar ed17ae9ce9cd88f5f6e1aff5ef91b584 ./server/bootstrapdependenciesJBAS5349-EJB2EntityCMP/lib/jbosscache-core.jar
and the hash of the file the AS built created was the same
faa2c964de0f06a7d0beb24cc58424ac ./jboss-as/thirdparty/jboss/cache/jbosscache-core/lib/jbosscache-core.jar
This must be a very easy fix just using the path to the correct jar.