maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MINVOKER-104) Error installing artifact's metadata
Date Tue, 29 Jun 2010 08:08:32 GMT

    [ http://jira.codehaus.org/browse/MINVOKER-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226618#action_226618
] 

Benjamin Bentmann commented on MINVOKER-104:
--------------------------------------------

The recommended practice for the Invoker is to use a private local repository somewhere inside
the project's output directory where concurrency concerns should not apply. Hence, I am tempted
to close this as won't fix.

> 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

        

Mime
View raw message