maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Wenig (JIRA)" <>
Subject [jira] Commented: (MINSTALL-54) [INFO] Error installing artifact's metadata
Date Sat, 26 Feb 2011 13:50:22 GMT


Michael Wenig commented on MINSTALL-54:

A similar problem did occur right now at our site

Using maven 22.1, Hudson 1.397 on a 8-core Linux-VM during release of one project. 

Previously we had fixed down the use of mave-parent:0.12 (with install-plugin:2.2/invoker:1.2)
via a dependcy-declaration.

We removed the maven-parent-version-lock (which was there for some unknown reasons) and the
error suddenly occured (now install:2.3 and invoker:1.5) are used.

Is the patch of Geoff planned to be integrated?

> [INFO] Error installing artifact's metadata
> -------------------------------------------
>                 Key: MINSTALL-54
>                 URL:
>             Project: Maven 2.x 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
> [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
> 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:
For more information on JIRA, see:


View raw message