Dependency Resolution Handling Conflicts with 2.0.8
---------------------------------------------------

                 Key: MNG-3606
                 URL: http://jira.codehaus.org/browse/MNG-3606
             Project: Maven 2
          Issue Type: Bug
          Components: Dependencies
    Affects Versions: 2.0.9
         Environment: # mvn -version
Maven version: 2.0.9
Java version: 1.5.0_14
OS name: "linux" version: "2.6.18-53.1.4.el5" arch: "i386" Family: "unix"

# java -version
java version "1.5.0_14"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_14-b03)
Java HotSpot(TM) Client VM (build 1.5.0_14-b03, mixed mode, sharing)
            Reporter: Andrew Lee Rubinger
         Attachments: #maven-chat.txt, maven_2.0.8_ejb3core.txt, 
maven_2.0.9_ejb3core.txt

The JBoss EJB3 Build has revealed dependency resolution differences between 
Maven 2.0.8 and 2.0.9.

In 2.0.8:

$> /opt/apache/maven/apache-maven-2.0.8/bin/mvn dependency:tree 
-Dincludes=org.jboss.microcontainer:jboss-container
[INFO] [dependency:tree]
[INFO] org.jboss.ejb3:jboss-ejb3-core:jar:0.1.2-SNAPSHOT
[INFO] \- org.jboss.jbossas:jboss-as-system-jmx:jar:5.0.0.Beta4:provided
[INFO] \- org.jboss.jbossas:jboss-as-jmx:jar:5.0.0.Beta4:provided
[INFO] \- org.jboss.microcontainer:jboss-container:jar:2.0.0.Beta10:provided 
(version managed from 2.0.0.Beta6)

$> /opt/apache/maven/apache-maven-2.0.8/bin/mvn -Dplugin=dependency 
help:describe
Group Id: org.apache.maven.plugins
Artifact Id: maven-dependency-plugin
Version: 2.0
Goal Prefix: dependency

In 2.0.9:

$> /opt/apache/maven/apache-maven-2.0.9/bin/mvn dependency:tree 
-Dincludes=org.jboss.microcontainer:jboss-container
{nothing}

$> /opt/apache/maven/apache-maven-2.0.9/bin/mvn -Dplugin=dependency 
help:describe
Group Id: org.apache.maven.plugins
Artifact Id: maven-dependency-plugin
Version: 2.0
Goal Prefix: dependency

These were run on the same machine from the same source tree.  As is shown 
above, "org.jboss.microcontainer:jboss-container" is not a dependency when 
using 2.0.9. 

Attached are the full outputs from the command "mvn -X dependency:resolve" for 
each Maven release.

This may be duplicated by running the JBoss EJB3 Build:

$> svn co https://svn.jboss.org/repos/jbossas/projects/ejb3/trunk
$> cd trunk
$> mvn clean install

The above must be done with the JBoss Repositories, typically this is done by 
making a a JBoss Profile in settings.xml as described by 
http://wiki.jboss.org/auth/wiki/MavenSettings

The concerning issue here is not whether this build passes or does not, but the 
fact that the build itself is proven to not be reproducible between 2.0.8 and 
2.0.9, a point release.  This either breaks backwards compatibility or is 
technically a bug fix, but either way makes a prime target for developer 
confusion.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to