You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Conny Kreyssel (JIRA)" <ji...@codehaus.org> on 2011/04/19 08:01:30 UTC

[jira] Commented: (MNG-4302) Physically separate plugins (and their dependencies) from project artifacts/dependencies in the local repository

    [ http://jira.codehaus.org/browse/MNG-4302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=263901#action_263901 ] 

Conny Kreyssel commented on MNG-4302:
-------------------------------------

Will this probably addressed in 3.1?

> Physically separate plugins (and their dependencies) from project artifacts/dependencies in the local repository
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4302
>                 URL: http://jira.codehaus.org/browse/MNG-4302
>             Project: Maven 2 & 3
>          Issue Type: New Feature
>          Components: Artifacts and Repositories
>            Reporter: Benjamin Bentmann
>             Fix For: Issues to be reviewed for 3.x
>
>
> This is basically a follow-up to MNG-4191. The separation on the remote side gets partly useless if we continue to store plugins and project artifacts in the same local repository. Once the artifacts have been locally cached by a former build, dependency resolution in another build can no longer detect whether it would have been able to resolve the same artifact remotely by the intended remote repos.

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