[jira] (MNG-4372) Unable to determine the release version on parallel execution

["Paul Benedict (JIRA)" <ji...@codehaus.org>]

     [ https://jira.codehaus.org/browse/MNG-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Benedict updated MNG-4372:
-------------------------------

    Fix Version/s:     (was: Issues to be reviewed for 3.x)

> Unable to determine the release version on parallel execution
> -------------------------------------------------------------
>
>                 Key: MNG-4372
>                 URL: https://jira.codehaus.org/browse/MNG-4372
>             Project: Maven
>          Issue Type: Bug
>         Environment: CentOS, Maven 2.1.0
>            Reporter: Patrik Kleindl
>
> We are building maven projects from Hudson with several workers.
> When two projects with the same parent (with version set to RELEASE) are built at the exact same time then both fail with:
> [INFO] Failed to resolve artifact.
> GroupId: com.***
> ArtifactId: ***
> Version: RELEASE
> Reason: Unable to determine the release version
>   ***:pom:RELEASE
> -----------------------------
> Known workarounds:
> - Start some seconds apart
> - Using explicit version instead of RELEASE
> It's not 100% reproducible but happens often enough to be annoying. When we had a larger number of projects using RELEASE this happened quite often.
> I will try to catch it in DEBUG mode, although this seems to affected the timing of the access.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)