[
https://issues.apache.org/jira/browse/MDEPLOY-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17136220#comment-17136220
]
Consultant Leon edited comment on MDEPLOY-254 at 6/16/20, 1:16 AM:
-------------------------------------------------------------------
I came to this page experiencing the same problem.
Shade plugin seems to generate sources jar with type jar and source plugin with
type 'sources' if I understand the issue well enough from the research I've
done.
I managed to disable the sources plugin in a subproject where issue occured
(duplicate deploy attempt of the -sources jar making the release build fail
where the develop build succeeded to deploy to snapshot repo...!).
It seems really strange that maven install/deploy cannot detect that exactly
the same file is being deployed twice and silently filter for this!
(it might be good to raise a warning if the same project artifact/attachment is
built more than once of course, but breaking only the release deploy seems very
badly behaved and it takes hours of investigation and clever workarounds to
then get your project released...)
BTW this problem occurs with maven 3.6.1 and on our jenkins 3.3.9. We used to
build with an older version, I recall 3.2.1? and have released the same project
successfully in the past, so I see this as a blocker regression bug.
was (Author: consultantleon):
I came to this page experiencing the same problem.
Shade plugin seems to generate sources jar with type jar and source plugin with
type 'sources' if I understand the issue well enough from the research I've
done.
I managed to disable the sources plugin in a subproject where issue occured
(duplicate deploy attempt of the -sources jar making the release build fail
where the develop build succeeded to deploy to snapshot repo...!).
It seems really strange that maven install/deploy cannot detect that exactly
the same file is being deployed twice and silently filter for this!
(it might be good to raise a warning if the same project artifact/attachment is
built more than once of course, but breaking only the release deploy seems very
badly behaved and it takes hours of investigation and clever workarounds to
then get your project released...)
> 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
>
> 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)
