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

[Pete Muir (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBSEAM-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Muir closed JBSEAM-3080.
-----------------------------

    Resolution: Out of Date


AS integration will now be hosted in the jboss as project

> Change xml-apis dependency to not include the jar
> -------------------------------------------------
>
>                 Key: JBSEAM-3080
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3080
>             Project: Seam
>          Issue Type: Task
>          Components: Build, Platform interoperability
>            Reporter: Mark Spritzler
>             Fix For: 2.0.3.CR2
>
>
> 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. ;)

-- 
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