[
https://issues.apache.org/jira/browse/MDEPLOY-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318877#comment-17318877
]
Alexander Kriegisch edited comment on MDEPLOY-254 at 4/11/21, 4:45 PM:
-----------------------------------------------------------------------
[~michael-o], I am afraid I do not understand your very terse previous comment.
What is here?
BTW, I just happened to notice that there is a release 3.8.1 now which is less
than a week old. Gonna try that one too.
*Update:* In Maven 3.8.1 the bug unfortunately is *not* fixed.
was (Author: kriegaex):
[~michael-o], I am afraid I do not understand your very terse previous comment.
What is here?
BTW, I just happened to notice that there is a release 3.8.1 now which is less
than a week old. Gonna try that one too. *Update:* In Maven 3.8.1 the bug
unfortunately is *not* fixed.
> 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)
