[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3080) Change xml-apis dependency to not include the jar

[ http://jira.jboss.com/jira/browse/JBSEAM-3080?page=all ] Mark Spritzler updated JBSEAM-3080: ----------------------------------- Description: In this mvn dependency graph it has the xml-apis jars to be included in a war which is build in Maven that has jboss-seam-jbas5 as a dependency. [INFO] +- org.jboss.seam:jboss-seam-jbas5:jar:2.0.1.GA:compile [INFO] | \- org.jboss:jboss-vfs:jar:2.0.0.Beta7:compile [INFO] | +- org.jboss:jboss-common-core:jar:2.2.3.GA:compile [INFO] | | +- apache-xerces:xml-apis:jar:2.7.1:compile [INFO] | | +- apache-httpclient:commons-httpclient:jar:2.0.2:compile [INFO] | | \- apache-slide:webdavlib:jar:2.0:compile [INFO] | \- jboss:jboss-common-logging-spi:jar:2.0.4.GA:compile This causes the war to fail to deploy on AS5. As a workaround the war pom can just add a dependency to the xml-apis but set its scope to "provided" to override the jboss-seam-jbas5 to. Well this might be down to jboss-common-core's pom that really needs fixing. it was just that Peter had said it was ok to open a Jira here. So blame him. ;) was: In this mvn dependency graph it has the xml-apis jars to be included in a war which is build in Maven and has jboss-seam-jbas5 as a dependency. [INFO] +- org.jboss.seam:jboss-seam-jbas5:jar:2.0.1.GA:compile [INFO] | \- org.jboss:jboss-vfs:jar:2.0.0.Beta7:compile [INFO] | +- org.jboss:jboss-common-core:jar:2.2.3.GA:compile [INFO] | | +- apache-xerces:xml-apis:jar:2.7.1:compile [INFO] | | +- apache-httpclient:commons-httpclient:jar:2.0.2:compile [INFO] | | \- apache-slide:webdavlib:jar:2.0:compile [INFO] | \- jboss:jboss-common-logging-spi:jar:2.0.4.GA:compile This causes the war to fail to deploy on AS5. As a workaround the war pom can just add a dependency to the xml-apis but set its scope to "provided" to override the jboss-seam-jbas5 to. Well this might be down to jboss-common-core's pom that really needs fixing. it was just that Peter had said it was ok to open a Jira here. So blame him. ;) -- 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