[jbosstools-issues] [JBoss JIRA] (JBIDE-15190) Saxon has dependency on org.jdom (Orbit) and dom4j (not p2-fied)

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-15190:
----------------------------------------

[~phantomjinx] [~nickboldt] This commit: https://github.com/mickaelistria/jbosstools-locus/commit/dfc0142fdfeffff7fce1fdbbd247e91578cc1bf3 trims the following package out of our saxon bundle:
* net.sf.saxon.dotnet
* net.sf.saxon.ant
* net.sf.saxon.option.dom4j
* net.sf.saxom.option.jdom
* net.sf.saxom.option.sql
* net.sf.saxon.option.xom

Ant, jdom, sql and xom could probably be added to the bundle by adding deps from the bundle to some other Orbit bundles. However, I think it makes more sense to just trim them out, and create some extension bundles for this specific extensions.

By the way, this change has for parent the suggested fix for JBIDE-15018 and is a valid for for JBIDE-15176.
                
> Saxon has dependency on org.jdom (Orbit) and dom4j (not p2-fied)
> ----------------------------------------------------------------
>
>                 Key: JBIDE-15190
>                 URL: https://issues.jboss.org/browse/JBIDE-15190
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: locus
>            Reporter: Mickael Istria
>
> Saxon has some transitive dependencies.
> * org.jdom is part of Orbit so it's easy to provide it
> * org.dom4j is not in any p2 repo (as far as I could search), and is available in its OSGi form via Maven. It also has transitive dependencies (Jaxen and some com.sun packages)
> This makes it difficult to create a nice artifact for Saxon...

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