[jboss-jira] [JBoss JIRA] (DROOLS-207) Transitive dependencies are not in sync with EAP: scannotation and xmlschema-core

[Geoffrey De Smet (JIRA)]

Geoffrey De Smet created DROOLS-207:
---------------------------------------

             Summary: Transitive dependencies are not in sync with EAP: scannotation and xmlschema-core
                 Key: DROOLS-207
                 URL: https://issues.jboss.org/browse/DROOLS-207
             Project: Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Geoffrey De Smet
            Assignee: Michael Biarnes Kiefer
            Priority: Minor


> EAP 6.1                               kie-wb.war
> ---------------------------------------------------------  
> scannotation-1.0.2-redhat-2.jar -->   dependency to 1.0.3
> xmlschema-core-2.0.2-redhat-2.jar --> dependency to 2.0.3
In theory this should not be able to happen.

A dependency:tree on kie-wb show this:
{code}
[INFO] org.kie:kie-wb-webapp:war:6.1.0-SNAPSHOT
...
[INFO] +- org.jbpm:jbpm-designer-backend:jar:6.1.0-SNAPSHOT:compile
...
[INFO] |  +- org.jbpm:jbpm-workitems:jar:6.1.0-SNAPSHOT:compile (version managed from 6.1.0-SNAPSHOT)
...
[INFO] |  |  \- org.apache.ws.xmlschema:xmlschema-core:jar:2.0.3:compile
{code}
and also
{code}
[INFO] org.kie:kie-wb-distribution-wars:pom:6.1.0-SNAPSHOT
...
[INFO] +- org.jboss.resteasy:resteasy-jaxrs:jar:2.3.6.Final:compile
[INFO] |  +- org.scannotation:scannotation:jar:1.0.3:compile
{code}

Investigate if any of those artifacts aren't messing with the transitive dependency version by overwriting their version. It's also possible that the bug is on the side of EAP (if they overwrite one of their transitive dependencies with a lower version).

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