[
http://jira.codehaus.org/browse/MOJO-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180463#action_180463
]
Josh McFarlane commented on MOJO-1383:
--------------------------------------
The only downside to this solution is if you have an external process (such as
Hudson) picking up the RPMs. Then, you have to modify the job based on the pom
name's rather than just a single static output folder.
Would it be possible to land the RPMs under a single output folder structure by
keeping old rpm/RPMS folder? So, you'd have separate ares for my-app-a and
my-app-b, but once my-app-a finished, it'd copy the contents of RPMS to the
target/rpm/RPMS, and then my-app-b would do the same once it finished? Then
you'd have separate build processes for each execution, but still one static
path to get the side-effect generated rpms.
> 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
