[ https://jira.jboss.org/jira/browse/JBAS-6251?page=com.atlassian.jira.plug... ] Alessio Soldano commented on JBAS-6251: --------------------------------------- http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBossWS-3.0.4.GA-te... The reason for most of the failures was that JBossWS 3.0.4.GA pom.xml files reference the thirdparty artifacts that were available when it was released. This means that the test classpath maven built by maven on client side used old versions (in particular of JBoss EJB3). I've uploaded a 3.0.4.SP1 version to the repository and changed the hudson job to use it on client side; 3.0.4.SP1 is basically the same as the GA version, just has few updated jboss component dependencies in the pom.xml files. I wouldn't mind updating the AS component matrix to use 3.0.4.SP1 as this is just a matter of how the client classpath is built to run the tests (real users are supposed to include the libraries provided by the AS), but if you want me to do that, it's not a problem (as, again, nothing was actually changed besides the thirdparty dependencies). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-6251?page=com.atlassian.jira.plug... ] Dimitris Andreadis closed JBAS-6251. ------------------------------------ I've already did, thanks Alessio! - <version.jboss.jbossws>3.0.4.GA</version.jboss.jbossws> + <version.jboss.jbossws>3.0.4.SP1</version.jboss.jbossws> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira