[jboss-jira] [JBoss JIRA] Commented: (JBRULES-992) Optional dependencies not marked as optional in maven pom xmls

[Geoffrey De Smet (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBRULES-992?page=comments#action_12375185 ] 
            
Geoffrey De Smet commented on JBRULES-992:
------------------------------------------

It depends on how xml apis are used by drools.
A) If drools just uses the javax.* interfaces, there's no need to add xerces,
B) If drools does use specific xerces classes, well jdk5 no longer includes the packages org.apache.xerces.* (sun now properly namespace them as com.sun.org.apache.xerces.*), so then xerces would be required.

Anyone know if it's A or B which is the case here?

> Optional dependencies not marked as optional in maven pom xmls
> --------------------------------------------------------------
>
>                 Key: JBRULES-992
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-992
>             Project: JBoss Rules
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions:  4.0.0.MR3
>         Environment: Maven 2.0.7
>            Reporter: Tuomas Kiviaho
>         Assigned To: Geoffrey De Smet
>             Fix For: 4.0.1
>
>         Attachments: pom.20070725.patch
>
>
> Slimming <http://markproctor.blogspot.com/2007/05/jboss-rules-even-slimmer.html> could be taken even further by marking optional dependencies listed in <http://anonsvn.labs.jboss.com/labs/jbossrules/trunk/README_DEPENDENCIES.txt> with <optional>true<optional/>.
> This would effectively remove transitional dependencies by default. Now I have to exclude them manually as a workaround. 
> Having xerces and xml-apis as transitive dependencies reminds me of commons-logging 1.1 situation where container/JDK provided packages emerge in wrong places of classpath hierarchy. Here endorsement via provided scope is in my opinion more appropriate. XPP3 could probably be replaced with StaxDriver, thus replacing one dependency with JDK provided dependency, but this goes already into implementation details.

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