[ http://jira.codehaus.org/browse/MNG-1635?page=all ]
John Casey updated MNG-1635:
----------------------------
Fix Version: 2.1
> replace custom artifact handling with direct calls to maven-artifact
> --------------------------------------------------------------------
>
> Key: MNG-1635
> URL: http://jira.codehaus.org/browse/MNG-1635
> Project: Maven 2
> Type: Task
> Components: Bootstrap & Build
> Reporter: Brett Porter
> Fix For: 2.1
>
>
> we should compile in maven-artifact to the bootstrap (just look in
> ../../maven-artifact/src/main/java for sources), since it has no dependencies.
> This can be used in place of the custom handling we have at the moment,
> particularly for transitive dependencies. The more of the metadata and
> snapshot handling we can push from maven-artifact-manager to maven-artifact
> without adding dependencies would be good too, so that m-a-m (not include in
> the bootstrap) is just the implementation classes that hook in maven-project,
> maven-repository-metadata and wagon, and the bootstrap can provide an
> alternative. Currently a lot of logic is in maven-artifact-manager.
--
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
