jira-importer commented on issue #149: URL: https://github.com/apache/maven-install-plugin/issues/149#issuecomment-2771841008
**[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** commented I'm actually more curious to the real cause of this issue. It seems like at the same time 2 installments of the same artifact is done. Isn't that kind of weird? For instance, with Jenkins, if a job is called multiple times, only one will be executed and the rest will be waiting in the queue. In most cases there's no need to do an `install`. Especially on buildserver, I'd run `clean verify` and let the build-server upload the artifacts to a repositorymanager. This way you are completely sure that other builds/developers can and will use the artifact as served by the repository manager (what is `deploy` fails?). If your buildserver has no such option, then run `mvn clean deploy -Dmaven.install.skip` Next, synchronization and IO are quite expensive, so this should be avoided as much as possible. So the default behavior should stay as it is. Now, the fact that the meta-data can get corrupt does mean that something needs to be fixed. When calling `install`, the files are passed to Maven-core, which is responsible for the actual copy to the local repository. So that's probably the best place where something needs to be fixed. -- 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
