[
https://jira.codehaus.org/browse/MDEP-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311744#comment-311744
]
Paul Gier edited comment on MDEP-383 at 10/17/12 10:02 PM:
-----------------------------------------------------------
Note, the reason that the purge-local-repository ITs pass even with Maven 3, is
because the test installs the artifacts locally instead of downloading from a
remote repo. This avoids the issue because the local metadata does not contain
the remote repo name.
was (Author: pgier):
Note, the reason that the purge-local-repository ITs pass, is because the
test installs the artifacts locally instead of downloading from a remote repo.
This avoids the issue because the local metadata does not contain the remote
repo name.
> Update purge-local-repository to work in Maven 3
> ------------------------------------------------
>
> Key: MDEP-383
> URL: https://jira.codehaus.org/browse/MDEP-383
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: purge-local-repository
> Affects Versions: 2.5.1
> Reporter: Paul Gier
> Assignee: Paul Gier
> Priority: Critical
> Fix For: 2.6
>
>
> The purge-local-repository goal currently uses an empty set of remote
> repositories when initially resolving the dependency set. This doesn't work
> in Maven 3 because the dependency resolution in Maven 3 is more strict about
> checking that an artifact has to be available in the current set of remote
> repositories, otherwise the resolution fails.
> {code:java}
> List<ArtifactRepository> remoteRepositories = Collections.emptyList();
> {code}
> This should be fixed to work with both Maven 2 and 3 if possible.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
