jira-importer commented on issue #187: URL: https://github.com/apache/maven-deploy-plugin/issues/187#issuecomment-2771513566
**[Alexander Kriegisch](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kriegaex)** commented This still happens with Maven 3.6.3 and Maven Shade with `<createSourcesJar>true</createSourcesJar>`. The thing is, if I do not configure Maven Source Plugin to run, I get lots of ugly conflict warnings during non-clean builds, because Maven Shade tries re-shading an already existing source JAR. The only way to avoid this is to even configure an additional ```xml <!-- Re-create original source JAR in order to avoid re-shading already shaded JAR in non-clean builds --> <forceCreation>true</forceCreation> ``` But then I get the duplicate uploads during deploy and e.g. on GitHub Packages an error like: ```java Transfer failed for (...)xyz-sources.jar 409 Conflict ``` This might be a conceptual problem in Maven itself, a shortcoming in Shade or Source, I really don't know and have no intention to get philosophical about something other people here know way more about. what I am sure about, though, is that this is a real problem many people are struggling with and nothing has happened to effectively fix it. Just sweeping this under the rug and closing it as "won't fix" because nobody dares to touch it certainly will not fix the problem. -- 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
