maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anders Hammar (JIRA)" <>
Subject [jira] (MDEP-398) Dependency resolution error with Maven 3
Date Tue, 12 Feb 2013 08:57:13 GMT


Anders Hammar updated MDEP-398:

    Environment: Maven 3.0.4, Mac OS X 10.8 and Windows 7  (was: Mac OS X 10.8, Windows 7)
        Summary: Dependency resolution error with Maven 3   (was: Maven 3 )
> Dependency resolution error with Maven 3 
> -----------------------------------------
>                 Key: MDEP-398
>                 URL:
>             Project: Maven 2.x Dependency Plugin
>          Issue Type: Bug
>         Environment: Maven 3.0.4, Mac OS X 10.8 and Windows 7
>            Reporter: Richard Vowles
>         Attachments: m3-dep2.1-tree-success.pom, m3-dep2.1-tree-success.txt, m3-dep2.6-failed.pom,
m3-dep2.6-failed.txt, m3-dep2.6-success.pom, m3-dep2.6-success.txt
> We are encountering an issue with Maven 3 dependency resolution (aether) that does not
occur with Maven 2. We need to get this issue resolved so we can use the resolved pom for
patch releases. 
> I have attempted to drop the pom.xml size down, but cannot do so too far without the
complex dependencies failing, I have spent many hours getting it this small. If there is a
member of the Maven team who is able to solve this kind of problem, we can supply access to
our Nexus to duplicate the problem. If there is any assistance on turning the log level of
Aether up so we could see what it is doing, that would also be appreciated.
> For this particular problem - at least two dependencies that should be there are missing.
Excluding the transitive dependencies on one of the dependencies makes them come back, but
that is not what should happen - exclusions change versions or remove dependencies - they
don't add them.
> We are encountering problems where dependencies that are not there get added, things
that should be there disappear and scopes (test -> compile) and versions change. 
> Attached are the three scenarios. 
> (1) Maven 3 - Dependency Plugin 2.6 - dep:list - Failure (2 x aspectj is not included)
> (2) Maven 3 - Dep 2.6 - dep:list - Success (2 x aspectj are included - pom is changed
to exclude transitive dependencies from one dependency)
> (3) Maven 3 - Dep 2.1 - dep:tree - Success (2 x aspectj are included - pom does not need
exclusions to make it work, it behaves as expected).
> Maven is run with -o -e -X 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message