cstamas commented on issue #11634: URL: https://github.com/apache/maven/issues/11634#issuecomment-3813352983
Both, NX and AF has/had issues, reported by users immediately when parallel PUT feature went out (3.9.1). Fx @bmarwell had a tweet about AF (I am not on it, and it does not allows me searching so I don't have link for tweet). In case of Nx2 staging suite things are a bit different: there, the deploy PUT requests are sent against "staging" endpoint and not against some repository. The feature was locally tested by me against Nx2 OSS instance (deploying to repository), and parallel PUT to repository works just fine. The Nx2 bug is limited to "staging feature" of Nx2 PRO ONLY. And about to "how should it know"": again, this is a special endpoint of Staging plugin. It receives requests, ties them logically, and, if needed, creates backing (staging, Nx managed) repository on the fly. The data points based on which are requests connected logically uses several properties of request: * user (as this endpoint requires authentication) * client IP address * client User Agent (will be same for all reqs -- ie Maven does not change UA between requests) * maybe some more, I don't remember Also, seems this is a _known issue_ of Nx2 staging, here is a gradle discussion about same issue: https://discuss.gradle.org/t/solving-multiple-staging-repositories-being-built-when-publishing-to-nexus/44834 -- 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]
