[jboss-jira] [JBoss JIRA] (JBEE-97) See if the jstl dependency on xalan can be refactored out

[Paul Gier (JIRA)]

    [ https://issues.jboss.org/browse/JBEE-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798327#comment-12798327 ] 

Paul Gier commented on JBEE-97:
-------------------------------

The problem with changing the groupId is that Maven has no concept of two GAs providing the same classes.  So if you put jboss jstl api and something else that depends on upstream xalan in your pom, you end up with two xalan jars in your classpath.  Depending on the size of the build it can be painful to exclude all locations of the wrong transitive dependency from getting into the dep tree/classpath.

                
> See if the jstl dependency on xalan can be refactored out
> ---------------------------------------------------------
>
>                 Key: JBEE-97
>                 URL: https://issues.jboss.org/browse/JBEE-97
>             Project: JBoss JavaEE Spec APIs
>          Issue Type: Enhancement
>          Components: jboss-jstl-api
>    Affects Versions: JavaEE 6 Spec APIs 3.0.0.Beta1
>            Reporter: Paul Gier
>            Assignee: Jason Greene
>             Fix For: JavaEE 7 Spec APIs 1.0.0.Beta1
>
>
> The JSTL api has a dependency on the xalan fork which is only available in the JBoss repository.  If this can be refactored out, then the complete set of dependencies will be available in central.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira