jira-importer commented on issue #502: URL: https://github.com/apache/maven-deploy-plugin/issues/502#issuecomment-2771546997
**[Martin Todorov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=carlspring)** commented In your case you're only referring to OS-s. However, this is a general classifier problem. What appears to be happening is that the .pom file gets re-deployed every time you want to invoke the deploy-file goal on the same artifactId but with a different classifier. I believe this behavior should be changed in such a way that if the artifact you're deploying has a classifier, then the plugin should check if the .pom has already been deployed to the remote host. If it has been, well, then just don't over-write it and things will be okay. It doesn't make sense to enable artifact re-deployment in your artifact repository manager just so that one could workaround this bug. Could somebody please have a look at this? Many thanks in advance! P.S.: I've tested this against 2.7. -- 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
