cstamas commented on issue #11634: URL: https://github.com/apache/maven/issues/11634#issuecomment-3813407348
Also, _to be clear_, the concurrency issue (IMO) exists only on "backward compatibility endpoint" (for maven-deploy-plugin), the well known `https://repository.apache.org/service/local/staging/deploy/maven2` as Staging Plugin has own [REST API](https://repository.apache.org/nexus-staging-plugin/default/docs/index.html) that is used among others by [Nx staging maven plugin](https://github.com/sonatype/nexus-maven-plugins/blob/main/staging/maven-plugin/README.md). Via REST you explicitly control the flow, you "start" staging (Nx creates repo for you, returns you the repo ID), then with received repo ID you perform direct deploy into newly created repository, close it, etc.... It is only the `/staging/deploy` endpoint that does this "magic" (grouping requests, selecting staging profile based on GAV, creating staging repository on the fly -- if needed, etc). This was also the reason we had to manually close and release (after successful vote) or drop, as all these actions can be triggered via REST as well... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
