[jira] (MINVOKER-104) Error installing artifact's metadata

["Robert Scholte (JIRA)" <ji...@codehaus.org>]

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

Robert Scholte closed MINVOKER-104.
-----------------------------------

    Resolution: Won't Fix
      Assignee: Robert Scholte

I agree with Benjamin.
Also, when comparing the overhead/costs of IO, synchronized methods (which only works within the same JVM), sleeps and timeouts with the chance that this situation occurs, IMHO it's not worth it.

                
> Error installing artifact's metadata
> ------------------------------------
>
>                 Key: MINVOKER-104
>                 URL: https://jira.codehaus.org/browse/MINVOKER-104
>             Project: Maven 2.x Invoker Plugin
>          Issue Type: Bug
>            Reporter: Geoff Simpson
>            Assignee: Robert Scholte
>            Priority: Critical
>         Attachments: minstall-54-error-install-artifact.patch
>
>
> Error installing artifact's metadata: Error installing metadata: Error updating group repository metadata
> end tag not allowed in epilog but got / (position: END_TAG seen ...\n
> Looks like there might be an issue with updates to maven-metadata-local.xml during the mvn install task. we have a build server that is multi threaded. we often see this in the
> </versioning>
> </metadata>
> </metadata>
> maven-metadata-local.xml.
> maybe a solution is to add maven-metadata-local.xml.lock to ensure two threads don't update the file at the same time

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira