[
https://issues.apache.org/jira/browse/MDEPLOY-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17316474#comment-17316474
]
Alexander Kriegisch commented on MDEPLOY-254:
---------------------------------------------
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.
> Maven Deploy Plugin deploy jar twice : Maven 3.3.3
> --------------------------------------------------
>
> Key: MDEPLOY-254
> URL: https://issues.apache.org/jira/browse/MDEPLOY-254
> Project: Maven Deploy Plugin
> Issue Type: Bug
> Reporter: Akshay
> Assignee: Karl Heinz Marbaise
> Priority: Blocker
> Fix For: waiting-for-feedback, wontfix-candidate
>
> Attachments: log1-mvn_clean_deploy_-Ptwice-source-jar-goal.txt,
> log2-mvn_clean_deploy_-Psource-and-shade-plugin.txt, sample-project.zip
>
>
> Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on
> project ****** :
> Failed to retrieve remote metadata ******/maven-metadata.xml:
> Could not transfer metadata ****** from/to ******
> {color:#FF0000} Not authorized , ReasonPhrase:Unauthorized. {color}
>
> Wanted to know if the fix is out in a later version of Maven?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
