[
https://issues.apache.org/jira/browse/MDEPLOY-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681131#comment-17681131
]
Slawomir Jaranowski commented on MDEPLOY-204:
---------------------------------------------
Currently maven-metadata is managed by Resolver, m-deploy-p doesn't create it.
I hope that this was resolved by MDEPLOY-296
> Must deploy maven-metadata.xml last
> -----------------------------------
>
> Key: MDEPLOY-204
> URL: https://issues.apache.org/jira/browse/MDEPLOY-204
> Project: Maven Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy
> Affects Versions: 2.8.2
> Reporter: Dan Tran
> Priority: Major
>
> 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
(v8.20.10#820010)
