maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nikolas Falco (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MDEPLOY-254) Maven Deploy Plugin deploy jar twice : Maven 3.3.3
Date Mon, 20 May 2019 07:39:00 GMT

    [ https://issues.apache.org/jira/browse/MDEPLOY-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16843730#comment-16843730
] 

Nikolas Falco commented on MDEPLOY-254:
---------------------------------------

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.

> 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
(v7.6.3#76005)

Mime
View raw message