[
http://jira.codehaus.org/browse/MOJO-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180401#action_180401 ]
Brett Okken commented on MOJO-1383:
-----------------------------------
You are correct, the usage of the <name> configuration will create 2 different rpms.
What if, instead of deleting the buildroot, each execution had its own workarea? This would support both your use case and the case of having multiple executions using the attached-rpm goal. In this case simply deleting the buildroot may not be an option as multiple rpms with the same "name" (but different classifiers) could be created.
In your example, the workarea would have 1 folder for each execution:
my-app-a
my-app-b
The buildroot, SPECS and RPMS and other folders would be created below those folders.
> Clear buildroot before copying files into folder
> ------------------------------------------------
>
> Key: MOJO-1383
> URL:
http://jira.codehaus.org/browse/MOJO-1383> Project: Mojo
> Issue Type: Bug
> Components: rpm
> Reporter: Josh McFarlane
> Assignee: Brett Okken
> Attachments: MOJO-1383.patch
>
>
> When you have multiple executions, the plugin does not clean out the buildroot folder prior to copying anything in for executions. This means the first execution will run fine, but any executions after that will fail due to files that are in buildroot but not consumed by the current rpm spec.
--
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
