Bug 956589

Summary: Wrong dependency management of jbossjts-jacorb artifact
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Jan Martiska <jmartisk>
Component: Maven RepositoryAssignee: Paul Gier <pgier>
Status: CLOSED WONTFIX QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: nziakova
Target Milestone: ---   
Target Release: EAP 6.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-09 18:31:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jan Martiska 2013-04-25 09:26:02 UTC 
When working with maven repository zip of 6.1.0.ER5, I found these issues:

$MAVEN_REPO/org/jboss/jbossts/jts/jbossjts-jacorb/4.17.3.Final-redhat-1/jbossjts-jacorb-4.17.3.Final-redhat-1.pom :
- version numbers of dependencies are hardcoded, should be using BOM instead
- there is a dependency on org.hornetq:hornetq-core:2.2.23.Final-redhat-1, which is from 6.0.1 (probably) and cannot be resolved in the 6.1.0.ER5 maven repository
Comment 1 Paul Gier 2013-09-13 14:29:58 UTC 
This is caused by the use of the maven shade plugin in the jbossts build.  The shade plugin automatically updates the pom with the dependency versions used while building.

Fixing this would require some significant changes to the upstream build, so it probably won't be fixed until the next major release of JBossTS/Narayana:
https://issues.jboss.org/browse/JBTM-1789
Comment 2 Paul Gier 2013-10-09 18:31:55 UTC 
Closing this one as DEFERRED because this is dependent on changes to the upstream Narayana/JBossTS build.  It should be fixed in the next major jbossts upgrade.