[
http://jira.codehaus.org/browse/MOJO-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180467#action_180467 ]
Brett Okken commented on MOJO-1383:
-----------------------------------
True.
However, that could be mitigated by using the attached-rpm goal and telling your external process to pull the secondary artifacts (the rpms) from your maven repository.
My concern is that I would like to have consistent behavior for all executions, regardless of goal (rpm vs. attached-rpm).
While copying stuff around would be possible for different names, when using the attached-rpm goal, different names are not be required, and copying will not work.
> 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
