Hi,
starting with Maven 3.9.12, for the Apache Camel project, we have several 
staging repositories created when trying to deploy.
It works fine with Maven 3.9.11.
It usually creates 4 or 5 staging repositories, 1 with almost all dependencies 
and the others with a single artifact. From observation, for the single 
artifact staging repositories, it was always some (but not all) artifacts from 
the top-level project. it is the first artifacts uploaded.
comparing Maven log when using 3.9.11 and 3.9.12, we can notice that with 
3.9.12, the parallel upload is starting faster (despite maven-deploy-plugin 
version is both 3.1.4):
with Maven 3.9.11:
[INFO] [INFO] --- deploy:3.1.4:deploy (default-deploy) @ camel ---
[INFO] Uploading to apache.releases.https: 
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/camel/camel/4.17.0/camel-4.17.0.pom
[INFO] Progress (1): 24 kB
[INFO]
[INFO] Uploaded to apache.releases.https: 
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/camel/camel/4.17.0/camel-4.17.0.pom
 (24 kB at 13 kB/s)
[INFO] Uploading to apache.releases.https: 
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/camel/camel/4.17.0/camel-4.17.0-source-release.zip
[INFO] Uploading to apache.releases.https: 
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/camel/camel/4.17.0/camel-4.17.0-cyclonedx.xml
[INFO] Uploading to apache.releases.https: 
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/camel/camel/4.17.0/camel-4.17.0-cyclonedx.json
[INFO] Uploading to apache.releases.https: 
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/camel/camel/4.17.0/camel-4.17.0-source-release.zip.sha512
[INFO] Uploading to apache.releases.https: 
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/camel/camel/4.17.0/camel-4.17.0.pom.asc
[INFO] Progress (1): 0/87 MB
[INFO] Progress (1): 0.1/87 MB
[INFO] Progress (1): 0.1/87 MB
[INFO] Progress (1): 0.1/87 MB
[INFO] Progress (1): 0.2/87 MB
[INFO] Progress (1): 0.2/87 MB
[INFO] Progress (1): 0.2/87 MB
[INFO] Progress (1): 0.3/87 MB
[INFO] Progress (1): 0.3/87 MB
[INFO] Progress (1): 0.3/87 MB
[INFO] Progress (1): 0.4/87 MB
[INFO] Progress (1): 0.4/87 MB
[INFO] Progress (1): 0.4/87 MB
[INFO] Progress (1): 0.5/87 MB
[INFO] Progress (1): 0.5/87 MB
[INFO] Progress (1): 0.5/87 MB
[INFO] Progress (1): 0.6/87 MB
[INFO] Progress (1): 0.6/87 MB
[INFO] Progress (2): 0.6/87 MB | 228 B
[INFO] Progress (2): 0.6/87 MB | 228 B
[INFO] Progress (3): 0.6/87 MB | 228 B | 0/8.3 MB
[INFO] Progress (3): 0.6/87 MB | 228 B | 0.1/8.3 MB
[INFO] Progress (3): 0.6/87 MB | 228 B | 0.1/8.3 MB
[INFO] Progress (4): 0.6/87 MB | 228 B | 0.1/8.3 MB | 128 B
[INFO] Progress (5): 0.6/87 MB | 228 B | 0.1/8.3 MB | 128 B | 0/7.8 MB
With Maven 3.9.12:
[INFO] [INFO] --- deploy:3.1.4:deploy (default-deploy) @ camel ---
[INFO] Uploading to apache.releases.https: 
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/camel/camel/4.17.0/camel-4.17.0.pom
[INFO] Uploading to apache.releases.https: 
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/camel/camel/4.17.0/camel-4.17.0-source-release.zip.sha512
[INFO] Uploading to apache.releases.https: 
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/camel/camel/4.17.0/camel-4.17.0-source-release.zip
[INFO] Uploading to apache.releases.https: 
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/camel/camel/4.17.0/camel-4.17.0-cyclonedx.json
[INFO] Uploading to apache.releases.https: 
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/camel/camel/4.17.0/camel-4.17.0-cyclonedx.xml
[INFO] Progress (1): 128 B
[INFO] Progress (2): 128 B | 0/7.8 MB
[INFO] Progress (3): 128 B | 0/7.8 MB | 0/87 MB
[INFO] Progress (4): 128 B | 0/7.8 MB | 0/87 MB | 0/8.3 MB
Is it a know issue?
I'm wondering if the reason is that the parallel upload is starting faster with 
Maven 3.9.12 causing Nexus to receive several requests too close and when 
checking if there is an existing repository, these several requests are not 
finding one and start to create a new staging repository.
Could it be a reason?
Any ideas for a configuration to avoid that?
Could you explain how/where the detection for creating a new staging 
repositories or not is done?
for reference the Apache Camel issue 
https://issues.apache.org/jira/browse/CAMEL-22826
the Nexus repository is https://repository.apache.org/ , the version is 
2.15.2-03
Note that I was unable to find from where the message "Uploading to XXX" is 
coming, the search on Apache org 
https://github.com/search?q=org%3Aapache+%2F%28%3F-i%29Uploading+to%2F&type=code
 didn't gave me a useful pointers.

Regards,


Aurélien Pupier, Senior Software Engineer for Apache Camel Quarkus

Unless otherwise stated above:

Compagnie IBM France
Siège Social : 17, avenue de l'Europe, 92275 Bois-Colombes Cedex
RCS Nanterre 552 118 465
Forme Sociale : S.A.S.
Capital Social : 664 614 175,50 €
SIRET : 552 118 465 03644 - Code NAF 6203Z

Reply via email to