You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Joerg Buchberger (JIRA)" <ji...@codehaus.org> on 2007/01/18 11:23:09 UTC

[jira] Commented: (MECLIPSE-152) Write .classpath with ordered dependencies [incl. Patch]

    [ http://jira.codehaus.org/browse/MECLIPSE-152?page=comments#action_85342 ] 
            
Joerg Buchberger commented on MECLIPSE-152:
-------------------------------------------

As for the convenience of finding particular dependencies in eclipse build path more quickly, I'd suggest the following 
SORT OPTIONS:
- by artifactId
- by groupId

However, I consider it more important to have the option to control CLASSPATH ORDER by sorting classpath entries
according to the order of dependencies as written in the POM. At least for runtime dependencies. 
This would make it unnecessary to manually adjust classpath order in eclipse and reduce time for supporting
developers who are unexperienced or new to the project...

> Write .classpath with ordered dependencies [incl. Patch]
> --------------------------------------------------------
>
>                 Key: MECLIPSE-152
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-152
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.2
>         Environment: Windowz XP, eclipse 3.2
>            Reporter: Holger Hoffstätte
>         Assigned To: Kenney Westerhof
>             Fix For: 2.4
>
>         Attachments: orderDependencies.patch, orderDependencies.patch
>
>
> Related to my comment in MNG-1412 - I decided to take a quick stab at the eclipse plugin and voilá! Ordered dependencies in the written .classpath. This is only a prototype (my first attempt at maven development) and could serve as basis for other orderings like groupId, transitive nearness etc.
> Initially I wanted to make IdeDependency comparable (similar to MECLIPSE-150 which added proper equals) but having multiple Comparators seemed better for extensibility.
> It worked right away, does exactly what I want (ordering by artifactId) and has minimal impact. I am not familiar with the maven codebase so I hope this is the right place to do the actual ordering before writing; obviously it should observe a property like -DorderDependencies=artifactId or something similar. The patch is against svn r425750 (2006-08-30). Currently no testcase but if someone tells me how to add/read an orderDependencies property I might add one.
> Comments welcome.

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