[
http://jira.codehaus.org/browse/MOJO-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162083#action_162083 ]
Brett Okken commented on MOJO-1218:
-----------------------------------
It is important to note that if you are creating the rpm as a primary or secondary artifact, the name of the file as it is deployed to the maven repository cannot be changed.
It will be <artifactId>-<version>.rpm for a primary artifact and <artifactId>-<version>-<classifier>.rpm for secondary artifact.
For a primary artifact the project.build.finalName also has impact on how the artifact is handled by maven.
> Add support for specifying the name of the rpm
> ----------------------------------------------
>
> Key: MOJO-1218
> URL:
http://jira.codehaus.org/browse/MOJO-1218> Project: Mojo
> Issue Type: Improvement
> Components: rpm
> Reporter: Erik Drolshammer
>
> AFAIK the plugin not use artifactID as the name of the final artifact. When creating separate deployment projects for each "product", this is unfortunate as I want to use the original name postfixed with "-rpm" for the artifactID, but keep the original name only (without the postfix) for the .rpm-file.
> Would it be possible to add a property to override the default final name of the rpm artifact?
--
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
