[jira] (MINSTALL-54) [INFO] Error installing artifact's metadata

["Dennis Lundberg (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MINSTALL-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=347777#comment-347777 ] 

Dennis Lundberg commented on MINSTALL-54:
-----------------------------------------

There seems to be a connection between MNG-5307 and MINSTALL-54. Reading through all the comments in both issues, and experiencing the issues myself, here are my conclusions.

In MNG-5307 people are running Maven in multi threaded mode. In this issue people are running Maven without multi threading, but on a build server. Going through the logs on our build server (Jenkins) made me realize that we are running several builds of the same code using a @daily schedule. There are several builds because they use different combinations of Maven and Java.

So there seems to be a problem when several processes are concurrently modifying the meta data files. Either using multiple threads in Maven or running multiple jobs on a build server. I don't know if the problem is in the Install Plugin or Maven Core though.

> [INFO] Error installing artifact's metadata
> -------------------------------------------
>
>                 Key: MINSTALL-54
>                 URL: https://jira.codehaus.org/browse/MINSTALL-54
>             Project: Maven Install Plugin
>          Issue Type: Bug
>          Components: install:install
>    Affects Versions: 2.2
>         Environment: Windows XP
>            Reporter: geoff simpson
>         Attachments: minstall-54-error-install-artifact.patch
>
>
> {noformat}
> [INFO] 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
> {noformat}
> 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 
> {code:xml}
> </versioning>
> </metadata>
> </metadata>
> {code}
> {{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 was sent by Atlassian JIRA
(v6.1.6#6162)