jira-importer commented on issue #544: URL: https://github.com/apache/maven-deploy-plugin/issues/544#issuecomment-2771550465
**[Nikolas Falco](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=nfalco79)** commented I have the same blocking issue with/with deployAtTheEnd configured. In my case happens when: 1. the source:jar goal is defined twice (for mistake the goal is duplicated), but I expect just only one deploy is performed (because the file is the same) 2. when the shade plugin is configured with createSourcesJar true, during the release:prepare/perform goals it perform the source:jar goal (that create a jar with sources in the project) and than shade plugin replace the original source artifacts (adding sources of shaded artifacts) Both scenario causes multiple attachment to the current MavenProject for the same file and gav +classifier +type. I expect that the processed ProjectDeployerRequest should be validated to avoid duplicate deploy if the same artifact (file + maven coordinate) that has been already deployed. Our maven repository (artifactory) is configured to deny override/replace already deployed artifacts (to ensure the artifact is unique and not modifiable). Do you need an example project? -- 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
