[jboss-jira] [JBoss JIRA] (JBBUILD-708) Missing Dependency in xalan-2.7.1.jbossorg-1.pom

[Paul Gier (Closed) (JIRA)]

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

Paul Gier closed JBBUILD-708.
-----------------------------

    Resolution: Done


You're right this xalan pom is broken.  The workaround is to use dependencyManagement to set the correct version of xalan:serializer.  I released a new version (2.7.1.jbossorg-2) with the correct dependency version in the pom.
https://repository.jboss.org/nexus/content/groups/public/xalan/xalan/2.7.1.jbossorg-2/
                
> Missing Dependency in xalan-2.7.1.jbossorg-1.pom
> ------------------------------------------------
>
>                 Key: JBBUILD-708
>                 URL: https://issues.jboss.org/browse/JBBUILD-708
>             Project: JBoss Build System
>          Issue Type: Bug
>          Components: Artifact Repositories
>            Reporter: Florian R.
>            Assignee: Paul Gier
>             Fix For: Build Support 2011
>
>
> The file
> https://repository.jboss.org/nexus/service/local/repositories/thirdparty-releases/content/xalan/xalan/2.7.1.jbossorg-1/xalan-2.7.1.jbossorg-1.pom
> uses a dependency xalan:serializer:2.7.1-jbossorg-1 but in the repository it is named xalan:serializer:2.7.1.jbossorg-1 (using a point intead of a hyphen).
> Using the artifact or if it gets resolved by maven transitive e.g. for xalan:xalan:[2.4.0,2.7.0) this fails a build. Could you please at least make a copy to xalan:serializer:2.7.1.jbossorg-1:jar and update+copy the pom.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira