[
http://jira.codehaus.org/browse/MBUILDHELPER-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251157#action_251157
]
Dan Tran commented on MBUILDHELPER-25:
--------------------------------------
Ultimately, 2 maven projects concurrently built using the same local repo is
the problem. Not recommend to do so
> Add removeCritical option to the RemoveLocalArtifactMojo
> --------------------------------------------------------
>
> Key: MBUILDHELPER-25
> URL: http://jira.codehaus.org/browse/MBUILDHELPER-25
> Project: Maven 2.x Build Helper Plugin
> Issue Type: New Feature
> Affects Versions: 1.5
> Environment: Windows, Java 6, Maven 2.2.1
> Reporter: Anthony Whitford
> Attachments: RemoveLocalArtifactMojo-removeCritical.patch
>
>
> My corporate parent pom has a step to run
> {{build-helper:remove-project-artifact}} which helps avoid local repositories
> from growing out of control.
> Occasionally, my continuous integration server fails when two projects are
> building at the same time that have a dependency. For example, Project A
> depends on Project B, and if Project B is trying to remove its artifact(s)
> while Project A is building, then the step fails. The failures are a
> nuisance.
> I propose adding a {{removeCritical}} flag to the {{RemoveLocalArtifactMojo}}
> that can control whether a failure is critical or not. In my case, I would
> like to _try_ and run the cleanup, but if it fails, a warning is OK and I'd
> like Maven to just continue... (After all, it may be successful on a follow
> up build.)
--
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
