[jboss-jira] [JBoss JIRA] Created: (JBBUILD-323) JBossBuild needs to be able to calculate component version using highest common denominator algorithm

[Alex Pinkin (JIRA)]

JBossBuild needs to be able to calculate component version using highest common denominator algorithm
-----------------------------------------------------------------------------------------------------

                 Key: JBBUILD-323
                 URL: http://jira.jboss.com/jira/browse/JBBUILD-323
             Project: JBoss Build System
          Issue Type: Feature Request
    Affects Versions: JBossBuild-1.1 DR2
            Reporter: Alex Pinkin


We've already had this discussion, and thought that it's not easy to implement. However, I do think we need this done since I don't want all projects to enumerate all their 3rd party dependencies in build-thirdparty.xml.

Example: these products include the following javassist versions

1. aop 1.5.0.GA:     javassist 3.2.0.CR1, 3.2.0.CR2, 3.3.0.GA
2. ws 1.0.0.GA:       javassist 3.2.0.CR1, 3.2.0.CR2, 3.3.0.GA
3. ejb3 1.0.0.CR8: javassist 3.2.0.CR1, 3.2.0.CR2, 3.2.0.GA

JBossBuild needs to be able to determine that javassist 3.2.0.CR2 is the highest common denominator. Current behaviour is that JBossBuild takes the highest version of the component whenever it runs into it for the first time during the dependency graph traversal.

Does Maven already support this? It seems like this should be one of the core maven features. 

Could you please look more info feasibility of implementing this in JBossBuild?

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