jira-importer commented on issue #187: URL: https://github.com/apache/maven-deploy-plugin/issues/187#issuecomment-2771513568
**[Alexander Kriegisch](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kriegaex)** commented I tried to deactivate Maven Source plugin, but in combination with Maven Shade that means that only dependency sources will be shaded, not own ones. So currently there is no other way than to run both Source + Shade if I want a shaded JAR with (possibly relocated) combined sources of the module itself and its dependencies. But then inevitably Deploy fails because it tries to deploy two source JARs with identical names. Please, if someone knows a (not too hacky) workaround, let me know. I cannot afford failing deployments because of this. Just to confirm: My build has no duplicate executions of Maven Source, both the effective POM and the build log confirm that. -- 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
