[jira] [Commented] (MDEPLOY-204) Must deploy maven-metadata.xml last

["Dan Tran (JIRA)" <ji...@apache.org>]

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

Dan Tran commented on MDEPLOY-204:
----------------------------------

This is a tough fix since it requires aether changes.  The good news is aether has the entire list of artifacts so that it can correctly reorder the deployments

> Must deploy maven-metadata.xml last
> -----------------------------------
>
>                 Key: MDEPLOY-204
>                 URL: https://issues.apache.org/jira/browse/MDEPLOY-204
>             Project: Maven Deploy Plugin
>          Issue Type: Improvement
>          Components: deploy:deploy
>    Affects Versions: 2.8.2
>            Reporter: Dan Tran
>
> For 'pom' project with large attachment.  The maven-metadata.xml get uploaded before the large attachment.  This creates a race condition where another maven requests for latest snapshot while the large upload still in progress, encounters file/resource not found error
> For none pom packaging ( jar, etc) without attachement,  the maven-metadata.xml always upload last
> detail discussion at http://maven.40175.n5.nabble.com/maven-metadata-xml-should-be-deployed-last-tt5858382.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)