[jira] Updated: (MSHARED-165) Update to use Maven3

["Mark Hobson (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MSHARED-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Hobson updated MSHARED-165:
--------------------------------

    Fix Version/s: maven-runtime 1.0-alpha-3

> Update to use Maven3
> --------------------
>
>                 Key: MSHARED-165
>                 URL: http://jira.codehaus.org/browse/MSHARED-165
>             Project: Maven Shared Components
>          Issue Type: Improvement
>          Components: maven-runtime
>    Affects Versions: maven-runtime 1.0-alpha-1
>            Reporter: Mark Hobson
>             Fix For: maven-runtime 1.0-alpha-3
>
>
> We currently depend on maven-project:2.0.8, but with Maven3 about to be released we should upgrade our dependencies to 3.0.  In Maven3, maven-project has been moved into maven-core:3.0.
> Maven3 also brings in changes to {{ProjectSorter}} via MNG-3814.  This means that versions are considered when ordering dependencies.  This affects maven-runtime as only the mediated version of a dependency is available at runtime and thus vertices of the runtime dependency graph can be neglected, leading to incorrect ordering from {{MavenRuntime.getSortedProjects}}.
> To resolve this we need to inject the runtime version of all discovered artifacts into the parsed {{MavenProjects}} prior to sorting.  This will emulate the situation that we have at runtime.

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