not sure if this is the cause of multiple staging repos appearing in ec2-hosted builds, but it can't help.
meanwhile I'm still trying to debug why create-release doesn't get hadoop-azure and hadoop-aws into the tarball, as it looks like they get into the hadoop-dist/target/hadoop-3.4.3/ tree. at 2h a build on my little pi5, this is very much a background project. ---------- Forwarded message --------- *From:* Andrew Wetmore <[email protected]> *Date:* 4 February 2026 at 18:20:36 GMT *To:* [email protected] *Subject:* *Parallel PUT problem in RAO with Maven 3.9.12* *Reply-To:* [email protected] Apache Maven 3.9.12 has a change that causes a problem in repository.apache.org (the Sonatype Nexus 2 Pro staging suite): if your build uses parallel PUT deployment, the build creates a separate staging repository for each of the requests instead of assembling everything in one repository. The Maven team is working on a resolution to this issue. Until the fix is available, they suggest disabling parallel PUTs. For details on disabling parallel PUTs, and what to do if you have already run into this problem in a build, see this article in the Infra blog: https://infra.apache.org/blog/parallelputissue.html Andrew Wetmore Technical Writer-Editor, Infra *Apache Software Foundation* <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free.www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#m_3015430651850810449_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
