You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Aurélien Pupier (Jira)" <ji...@apache.org> on 2026/01/08 11:00:00 UTC
[jira] [Commented] (CAMEL-22826) Upload release is creating several staging repositories
[ https://issues.apache.org/jira/browse/CAMEL-22826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18050598#comment-18050598 ]
Aurélien Pupier commented on CAMEL-22826:
-----------------------------------------
I checked that the artifact of th top-level project are pushed first. So wondering if it can be that the deploy started in // and the nexus repository is creating different staging repositories because each upload didn't notice that there is another one in creation. Maybe something started with newer Maven/Maven deploy plugin?
> Upload release is creating several staging repositories
> -------------------------------------------------------
>
> Key: CAMEL-22826
> URL: https://issues.apache.org/jira/browse/CAMEL-22826
> Project: Camel
> Issue Type: Task
> Affects Versions: 4.17.0
> Reporter: Aurélien Pupier
> Priority: Major
>
> It starte with Camel 4.17.0.
> A release of 4.14.4 was tried after and it went well.
> Both Gregor and Aurélien are able to reproduce this behavior.
> It usually creates 4 or 5 staging repositories, 1 with almost all dependencies and the pthers with a single artifact. From observation, for the single artifact staging repositories, it was always some (but not all) artefacts from the top-level project.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)