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

**[Geoff Simpson](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=gsimpson)** opened **[MINSTALL-54](https://issues.apache.org/jira/browse/MINSTALL-54?redirect=false)** and commented

```
[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

```xml

```

`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

---

**Affects:** 2.2

**Attachments:**
- [minstall-54-error-install-artifact.patch](https://issues.apache.org/jira/secure/attachment/12716599/minstall-54-error-install-artifact.patch) (_6.56 kB_)

**Issue Links:**
- [MINVOKER-104](https://issues.apache.org/jira/browse/MINVOKER-104) Error installing artifact's metadata

- [MNG-5307](https://issues.apache.org/jira/browse/MNG-5307) NPE during resolution of dependencies - parallel mode

15 votes, 25 watchers

Start by examining the mvn install path that updates maven-metadata-local.xml and reproduce the failure with parallel builds. The attached minstall-54-error-install-artifact.patch and the linked parallel-mode issues provide context. Done means concurrent installation no longer produces malformed metadata with duplicate closing tags.

Written by the indexing model from the issue text.