jira-importer commented on issue #149: URL: https://github.com/apache/maven-install-plugin/issues/149#issuecomment-2771841104
**[Dan Armbrust](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=armbrust)** commented Whenever someone mentions maven, and I curse under my breath, this bug report is now the most recent example of everything that is wrong with this project. We have a dumb bug, identified 8 years ago. A patch is provided years and years ago. And the maintainers can't even be bothered to apply it. Now that I have switched over to using pipeline builds with jenkins - when i do a release, it ends up building both master and development branches at the same time. Guess what happens when a build server tries to do two builds at the same time... good lord. What the heck is the point of having a local cache, if you can't use it in parallel? This should be part of the basic requirements..... The point of the cache is to save me from GB and GB of downloads. If I have to use a per-build cache, or reconfigure jenkins to have a per-instance cache, I'm wasting disk, bandwidth, slowing down all my builds, and making it impossible to build dependent code without having an artifact server running, since I can't rely on a mvn install from one instance making the latests snapshot code available to another instance. What is it going to take to get this fixed? Does someone need to remote in to a maintainers computer, and type the keystrokes for them to do the merge? Of course, at this point, since they ignored a patch that was supplied to them, I'm sure it will no longer apply cleanly. -- 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
