You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Slawomir Jaranowski (Jira)" <ji...@apache.org> on 2023/01/31 15:45:00 UTC

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

     [ https://issues.apache.org/jira/browse/MDEPLOY-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Slawomir Jaranowski reassigned MDEPLOY-204:
-------------------------------------------

    Assignee: Slawomir Jaranowski

> 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
>            Assignee: Slawomir Jaranowski
>            Priority: Major
>             Fix For: 3.1.0
>
>
> 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)