You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Geoff Simpson (JIRA)" <ji...@codehaus.org> on 2010/06/29 07:52:32 UTC
[jira] Commented: (MINVOKER-104) Error installing artifact's
metadata
[ http://jira.codehaus.org/browse/MINVOKER-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226615#action_226615 ]
Geoff Simpson commented on MINVOKER-104:
----------------------------------------
note that there is a duplicate report here http://jira.codehaus.org/browse/MINSTALL-54 but as the fix is inside this project i've raised a second bug report here.
> Error installing artifact's metadata
> ------------------------------------
>
> Key: MINVOKER-104
> URL: http://jira.codehaus.org/browse/MINVOKER-104
> Project: Maven 2.x Invoker Plugin
> Issue Type: Bug
> Reporter: Geoff Simpson
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira