jira-importer commented on issue #222: URL: https://github.com/apache/maven-deploy-plugin/issues/222#issuecomment-2771516352
**[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** commented That will the status of the current MavenProject. And I know that someone will ask for the same solution with the `maven-install-plugin`, so that should be a sign that this is not the correct solution. IMHO it is still wrong to use `deploy-file` as part of the build-lifecycle. These jars are static, so there's no need to upload them as part of the lifecycle, right? `deploy-file` was very useful in the past when there were no good repository manager GUIs which gave you the option to upload artifacts. However, I think there's indeed an issue with the code: it should not abuse the current `MavenProject`. It would be better to create a new MavenProject instance in case of the `deploy-file` goal. -- 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
