[
http://jira.codehaus.org/browse/MRPM-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189051#action_189051
]
Brett Okken commented on MRPM-42:
---------------------------------
Could the same thing be accomplished with the maven dependency plugin
(specifically the copy goal)?
http://maven.apache.org/plugins/maven-dependency-plugin/copy-mojo.html
> Add ability to specify an outputFileNameMapping for an included dependency
> --------------------------------------------------------------------------
>
> Key: MRPM-42
> URL: http://jira.codehaus.org/browse/MRPM-42
> Project: Mojo RPM Plugin
> Issue Type: New Feature
> Components: rpm
> Affects Versions: 2.0-beta-3
> Reporter: Luke Forehand
> Assignee: Brett Okken
>
> Use Case:
> Assembling an RPM that includes a WAR repository artifact.
> The RPM install script copies the versioned artifact to a server deployment
> location, where the WAR is automatically unpacked and deployed.
> Since the context path of the webapp is inferred from the filename of the WAR
> artifact, it is important for the filename to remain the same.
> Specifying an outputFileNameMapping for the dependency would allow the WAR
> artifact to be renamed before it was added to the RPM.
> I think there are probably other similar use cases. This feature exists in
> the maven-assembly-plugin.
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
