jira-importer commented on issue #154: URL: https://github.com/apache/maven-install-plugin/issues/154#issuecomment-2771841781
**[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** commented I'm not really convinced yet. If there are third party jars which are required to build the project, the preferred solution is a [repository manager](http://maven.apache.org/repository-management.html) where you can share such artifacts with your team. If that is too much overhead, re-read the article and ask yourself: is it really that much overhead? For those who still think they can't/shouldn't use a repository manager (and commit those binaries into a source countrol system), the `install-file` is a one-time only goal, since you don't want to re-install those files. In that case create a project responsible for only installing these artifacts or use a profile. I consider pom-properties as constants which can be shared. So that would mean that by default the install-file is always or never triggered. By introducing the `skip` parameter I predict more confusion, especially with new Maven users ("how can Maven know which files must be installed?? with install-file I'm in full control again"). -- 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
