jira-importer commented on issue #149: URL: https://github.com/apache/maven-install-plugin/issues/149#issuecomment-2771841153
**[Alan Czajkowski](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=alan-czajkowski)** commented [Geoff Simpson](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=gsimpson) [tibordigana](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=tibordigana) [Rocco De Angelis](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rdeangelis83) It appears that [Jonathan Woods](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jonw) has the most reasonable solution to this problem: by adding this to the build server's Maven `settings.xml` file: ``` <localRepository>${user.home}/.m2/repository-${env.EXECUTOR_NUMBER}/</localRepository> ``` This solution is specific to Jenkins, but can be ported to any other build system. You can't use a global cache because of the concurrent access (read & write) conflict. You don't want to use a Maven local cache per build because the performance of trying to download "the entire world" on every build would be too painful. So, the reasonable thing to do is the compromise: set the cache to be executor-specific that way you get a semi-global cache, but don't need to download the entire world every time, and you get the safety of the executor only being able to run sequentially (solving the concurrency problem). -- 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
