[
http://jira.codehaus.org/browse/MASSEMBLY-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed MASSEMBLY-231.
--------------------------------
Resolution: Won't Fix
Fix Version/s: (was: 2.3-beta-1)
Assignee: John Casey
out of scope; it's easy enough to define (in the deploy plugin, perhaps?) a
mojo that will scoop up a file - say, an assembly - from the target directory
and push it out to whatever location you want. This gets into provisioning from
a Maven build, though, which IMO is a dangerous area.
In any case, it's not in scope for the assembly plugin to get into the
distributionManagement section of the POM.
> Allow Assembly plugin to specify alternate DistributionManagement
> -----------------------------------------------------------------
>
> Key: MASSEMBLY-231
> URL: http://jira.codehaus.org/browse/MASSEMBLY-231
> Project: Maven 2.x Assembly Plugin
> Issue Type: Improvement
> Affects Versions: 2.2-beta-1
> Reporter: James William Dumay
> Assignee: John Casey
> Attachments: maven-assembly-plugin.patch,
> maven-assembly-plugin.patch, maven-assembly-plugin.patch,
> maven-assembly-plugin.patch
>
>
> The following patch allows the assembly plugin to specify alternate
> repository locations for deployment of its attached artifacts.
--
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
