jira-importer commented on issue #189: URL: https://github.com/apache/maven-install-plugin/issues/189#issuecomment-2771846980
**[Petr Kozelka](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pkozelka)** commented You are right that I can configure some sort of explicit purging at buildserver; but this issue mainly affects simple configurations without one. Even in a big team: people who want to make a build **before** commit, trying to avoid failure at CI build, are affected too. I am often explaining developers from my team why the build nicely passing on their local machine fails on CI server, and would be happy if one of the most frequent reasons could be eliminated IMHO the case when you need to just "update" repo is very infrequent. What about to make this functionality controlled by an option? Then, I can control this by corporate pom, and explicitly turn on "update" behavior for the few modules that need it. I can create a patch for this; please let me know if it sounds like acceptable way. -- 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
