[ https://issues.apache.org/jira/browse/MDEPLOY-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465925#comment-17465925 ]
Alexander Kriegisch commented on MDEPLOY-254: --------------------------------------------- {quote}Fix was delivered with Maven 3.8.2.{quote} I successfully verified this in my project, using Maven 3.8.2 and 3.8.4. Thank you for cherry-picking the fix. {quote}Nothing to be fixed here.{quote} I do not understand that part of your comment. Of course there was something to be fixed here, the bug was open since March 2019, i.e. more than 2.5 years. > 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 > Attachments: image-2021-04-11-23-55-48-005.png, > 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.20.1#820001)