[
http://jira.codehaus.org/browse/MNG-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James William Dumay updated MNG-3151:
-------------------------------------
Attachment: MNG-3151-maven-2.0.x.patch
Patch contains functional implementation of this issue.
The Artifact setRepository() and getRepository() have had their usage changed
so that depending on the context of their use, they are either the
ArtifactRepository that they originate from (eg, dependency) or where their
destination will be when the Artifact is deployed.
> Allow plugins that attach artifacts to specify deployment locations
> -------------------------------------------------------------------
>
> Key: MNG-3151
> URL: http://jira.codehaus.org/browse/MNG-3151
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories, General
> Affects Versions: 2.0.8
> Reporter: James William Dumay
> Attachments: MNG-3151-maven-2.0.x.patch
>
>
> The following patch allows plugins to specify Distribution Management
> relating to their attached artifacts.
> This is useful in large Java shops where, depending on the type of artifact
> (Javadoc, source, assembly, etc)m you may want to deploy these artifacts to
> different repositories (eg public and private).
--
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
