Resolve container integration naming issue ------------------------------------------ Key: JBWS-2230 URL: http://jira.jboss.com/jira/browse/JBWS-2230 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jbossws-cxf-3.0.2 we currently use jbossws-jboss421-3.0.2-SNAPSHOT jbossws-jboss422-3.0.2-SNAPSHOT jbossws-jboss423-3.0.2-SNAPSHOT jbossws-jboss500-3.0.2-SNAPSHOT jbossws-jboss501-3.0.2-SNAPSHOT This works on the premisses that jboss500 == jboss-5.0.0.Beta4 jboss501 == jboss-5.0.0.CR1 The naming scheme will however fail when CR1 gets released and container integration moves on towards CR2 or GA. It will also fail for jboss-4.2.2.SP1, etc More generally, this naming scheme does not support multiple versions for the same AS minor version. To fix this, we would need to factor the AS version into the naming scheme. Possibly like jbossws-jboss-5.0.0.Beta4-3.0.2-SNAPSHOT jbossws-jboss-5.0.0.CR1-3.0.2-SNAPSHOT This scheme would obviously support a matrix of multiple container versions against multiple jbossws versions, which is required according to http://jbws.dyndns.org/mediawiki/index.php?title=Supported_Target_Containers The above suggestion however fails, because maven does not support dependencies with multiple versions on the same artifact. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira