maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Holger Hoffstätte (JIRA) <>
Subject [jira] Commented: (MNG-1412) dependency sorting in classpath
Date Mon, 14 Aug 2006 17:05:50 GMT
    [ ] 
Holger Hoffstätte commented on MNG-1412:

I want to add another point of view and request ordering of exported jars *by name*, at least
as option. While I can understand Mark's use case for controlling export ordering (POM order
is a good step forward from the current way), I like to think of the need for a properly ordered
classpath as a build management bug in the first place. This should just not be an issue for
IDE development; I'd venture the guess that quickly finding classes in a list of jars is the
much more common case. 99% of the time I am simply not interested in detailed dependency trees,
and for launching I can still rearrange in the launch config.
Looking at the patches it seems to me that an optional name ordering should not be much more
complicated, e.g. by throwing everything into a TreeMap before output.

> dependency sorting in classpath
> -------------------------------
>                 Key: MNG-1412
>                 URL:
>             Project: Maven 2
>          Issue Type: Bug
>    Affects Versions: 2.0
>            Reporter: Mark Hobson
>         Assigned To: fabrizio giustina
>             Fix For: 2.1
>         Attachments: artifact-order_maven-artifact-manager.txt, artifact-order_maven-artifact.txt,
> 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