maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Herve Boutemy (JIRA)" <>
Subject [jira] Updated: (MNG-1412) dependency sorting in classpath
Date Sat, 02 Feb 2008 15:03:59 GMT


Herve Boutemy updated MNG-1412:

    Attachment: MNG-1412_dependency_sorting.tgz

I just wrote a JUnit test that proves the defect.

And it shows that the sorting problem was still here in 2.0.8, but it is not here any more
in 2.0.9-SNAPSHOT (I didn't check 2.1-SNAPSHOT).
I fixed it on 2007/12/07 in r601095 (r601096 in trunk) while working on such a dependencies
sorting issue in MANTTASKS-91: one HashSet to LinkedHashSet transformation had been forgotten...

Now I need to transform this JUnit test in an integration test to ensure that no regression
will happen in the future.

Can somebody check that it is ok for him with 2.0.9-SNAPSHOT? I'm pretty sure it is ok given
my JUnit test, but having someone confirm this would be even better.

> dependency sorting in classpath
> -------------------------------
>                 Key: MNG-1412
>                 URL:
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 2.0
>            Reporter: Mark Hobson
>            Assignee: fabrizio giustina
>             Fix For: 2.1
>         Attachments: artifact-order_maven-artifact-manager.txt, artifact-order_maven-artifact.txt,
artifact-order_maven-project.txt, MNG-1412-maven-2.0.x-r507746.patch, MNG-1412_dependency_sorting.tgz
> The .classpath file entries should be ordered by nearest transitiveness (if that's a
> For example, I have project A that depends on B that depends on C.  The classpath for
A is generated in the order C, B.  Ideally the classpath should be in order of how near they
are to the project, i.e. B, C.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message