You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2009/02/10 19:06:20 UTC
[jira] Closed: (MNG-4026) [regression] Order of project class path
does not match POM order during reactor build
[ http://jira.codehaus.org/browse/MNG-4026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-4026.
----------------------------------
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 2.1.0
Fixed in [r743034|http://svn.eu.apache.org/viewvc?view=rev&revision=743034].
> [regression] Order of project class path does not match POM order during reactor build
> --------------------------------------------------------------------------------------
>
> Key: MNG-4026
> URL: http://jira.codehaus.org/browse/MNG-4026
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 2.1.0
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Fix For: 2.1.0
>
>
> [r742799|http://svn.eu.apache.org/viewvc/maven/components/branches/maven-2.1.x/maven-project/src/main/java/org/apache/maven/project/MavenProject.java?view=diff&r1=742798&r2=742799&pathrev=742799] uses a {{HashSet}} for the dependencies and as such shuffles the class path. The ordering is only destroyed if dependeny resolution happens more than once for a project, i.e. a single plugin execution will not exhibit the issue.
--
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