jira-importer commented on issue #544: URL: https://github.com/apache/maven-deploy-plugin/issues/544#issuecomment-2771550505
**[Nikolas Falco](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=nfalco79)** commented I remember that the double execution typically happens during maven release plugin because it seems enable the sources goal by default. So If I define a custom source-plugin execution it will run twice. The source plugin it's just an example but it happens also with javadoc. This means patch any existing plugin. Anyway I do not agree with the proposed workaround because this means that it's no more possible contribute the content of an existing artifact using multiple execution like the maven-shade-plugin does. For example there is no way to obtain the same result of sources+shade plugins to reach the goal of a jar that contains both project sources and third party shaded sources unless perform a lot of work instead of a single configuration parameter. I would point the attention that for the maven-shade-plugin the double upload does not happens for the main jar (maven-jar-plugin), replaced by shade plugin in the same manner of sources jar. Is it possible check if two ProjectDeployerRequest refers to the same artifact and skip the upload only in that case? Because in teory the second upload does not have sense since the file and GAV are the same, this will speedup the deploy execution time and prevent also potential failures in upload. -- 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
