jira-importer commented on issue #149: URL: https://github.com/apache/maven-install-plugin/issues/149#issuecomment-2771841187
**[Gjøran Voldengen](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=gjoranv)** commented Like [Rocco De Angelis](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rdeangelis83) reports above, we also see this on a single multi-threaded maven build. This particular build is for a list of _maven plugins_, and it seems that each thread building a plugin tries to update the maven-metadata.xml file of the group it belongs to. If this is the case, a possible (but inconvenient) workaround could be to use a separate groupId for each plugin. Our project is open source, and the pom.xml file can be found here: https://github.com/vespa-engine/vespa/blob/master/maven-plugins/pom.xml Maven version: 3.6.3 maven-install-plugin:2.5.2 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
