jira-importer commented on issue #142: URL: https://github.com/apache/maven-install-plugin/issues/142#issuecomment-2771839961
**[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** commented Most artifacts have a `META-INF/maven/${groupId}/${artifactId}/pom.xml` which would mean these versions are out of sync. So the `install` phase is too late to fix the version. The issue of [danttran](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=danttran) seems to be with `install-file` rather than `install`. For continuous integration you shouldn't abuse the `pom.xml`, the file which contains the build-**instructions**. If you want to uniquely identify the build-**result** you can add a revision-number to the MANIFEST-file (see [buildnumber-maven-plugin](http://mojo.codehaus.org/buildnumber-maven-plugin/)) or add your custom file to the artifact. The main purpose of the local repository is to have a folder structure so other projects can refer to these artifacts by specifying a dependency, plugin, etc. IMHO for that same reason it is wrong to use this local repository as the location for distributable/deployables/end-products, since you'll never refer to these files. I'm pretty sure there are better solutions then specifying a version during the install. I noticed there are quite a lot of votes and watchers for this issue. I'd be glad to help those with a better more solid solution. -- 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
