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:03:00 UTC

[jira] [Updated] (CAMEL-22826) Upload release is creating several staging repositories

     [ https://issues.apache.org/jira/browse/CAMEL-22826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aurélien Pupier updated CAMEL-22826:
------------------------------------
    Description: 
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.

Revert of various Maven plugin version was tried.

One to try is to get back to Maven 3.9.11 in the Maven wrapper configuration

  was:
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.


> 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.
> Revert of various Maven plugin version was tried.
> One to try is to get back to Maven 3.9.11 in the Maven wrapper configuration



--
This message was sent by Atlassian Jira
(v8.20.10#820010)