Hi Ah so there is a problem/bug with Maven 3.9.12 https://github.com/apache/maven/releases/tag/maven-3.9.12
Not sure if there is anything standing out, but when other projects upgrade to 3.9.12, then MAVEN may get others reporting some issues if they end up with similar problems. On Thu, Jan 8, 2026 at 12:15 PM Gregor Zurowski <[email protected]> wrote: > After downgrading the Maven version (reverting the latest Maven > Wrapper upgrade), I was able to build the release without issues. I am > building the RC for 4.17.0 now. > > Thank you for your support! > > On Thu, Jan 8, 2026 at 12:02 PM Aurelien Pupier via dev > <[email protected]> wrote: > > > > I created this issue to gather information and help investigation: > > https://issues.apache.org/jira/browse/CAMEL-22826 > > > > Note that I was able to reproduce the behavior also on my side with > 4.17.0, so most probably discarding potential change in local environment. > > ________________________________ > > From: Gregor Zurowski <[email protected]> > > Sent: Thursday, January 8, 2026 9:34 AM > > To: [email protected] <[email protected]> > > Subject: [EXTERNAL] Re: Camel 4.17.0 Release > > > > Hi, > > > > I tried a couple of things yesterday (removing the override config for > > the release plugin and reverting versions of different release-related > > plugins), but with no luck. I will try it once more by reverting the > > wrapper. If this doesn't succeed, I believe we should be fine with > > having multiple staging repositories for this release. > > > > Thanks for your help. > > > > On Thu, Jan 8, 2026 at 8:54 AM Aurélien Pupier <[email protected]> > wrote: > > > > > > Another idea to try, revert the Maven version of Maven wrapper to > 3.9.11 as it was for the 4.16.0, or 3.9.9 as it was for 4.14.4 > > > > > > On 2026/01/07 15:05:20 Aurélien Pupier wrote: > > > > Hello, > > > > > > > > in fact, I'm wondering if we can publish the several staging > repositories > > > > in case we really want to. It all ends on maven central without > distinction > > > > from which staging repository it came as far as I know. > > > > > > > > That said, it is adding complexity to the release process and we > still(?) > > > > have time to investigate on the 4.17.0 (and non LTS) version various > > > > thingies instead of pushing to the LTS release > > > > > > > > On Wed, Jan 7, 2026 at 3:22 PM Claus Ibsen <[email protected]> > wrote: > > > > > > > > > Hi > > > > > > > > > > Thanks Aurelien for helping and the suggestions. > > > > > Fingers crossed that we can get this resolved soonish and be able > to do the > > > > > release, and be ready for the next LTS this quarter. > > > > > > > > > > > > > > > > > > > > On Wed, Jan 7, 2026 at 11:28 AM Aurelien Pupier via dev < > > > > > [email protected]> wrote: > > > > > > > > > > > Do you have the full log available so that we can put another > pair of > > > > > eyes > > > > > > on it? > > > > > > > > > > > > On the 4 repositories: > > > > > > > > > > > > * > > > > > > one contains almost everything > > > > > > * > > > > > > One contains only > org/apache/camel/camel/camel.4.17.0-source-release.zip > > > > > > * > > > > > > One contains only > > > > > > org/apache/camel/camel/camel.4.17.0-source-release.zip.sha512 > > > > > > * > > > > > > One contains only org/apache/camel/camel/camel-4.17.0.pom > > > > > > > > > > > > So seems only the top level project is causing troubles. > > > > > > I'm wondering what is creating the *source-release.zip, is it the > > > > > > maven-source-plugin or the maven-release-plugin. I have not > found where > > > > > the > > > > > > version of maven-source-plugin is specified to check if there > was a > > > > > change > > > > > > with this one. > > > > > > > > > > > > I added my PGP key but as i put the wrong fingerprint value > yesterday, I > > > > > > will have to wait tomorrow another sync ( > > > > > > https://people.apache.org/keys/committer/ < > > > > > > https://people.apache.org/keys/committer/ > ) in order to > potentially try > > > > > > also on my side. > > > > > > > > > > > > As mentioned by Andrea, looking to nexus-maven-plugin is a good > option to > > > > > > try too. > > > > > > > > > > > > ________________________________ > > > > > > From: Gregor Zurowski <[email protected]> > > > > > > Sent: Wednesday, January 7, 2026 10:54 AM > > > > > > To: [email protected] <[email protected]> > > > > > > Subject: [EXTERNAL] Re: Camel 4.17.0 Release > > > > > > > > > > > > I just attempted to release 4.17.0, and now I am seeing four > > > > > > repositories even on Camel core. It only happened with Camel > Spring > > > > > > Boot. I also verified the IP addresses, but they are the same > across > > > > > > all four staging repositories. > > > > > > > > > > > > On Wed, Jan 7, 2026 at 10:02 AM Claus Ibsen < > [email protected]> > > > > > wrote: > > > > > > > > > > > > > > Hi > > > > > > > > > > > > > > That is not a problem 4.17 is a short lived release and the > aim is to > > > > > get > > > > > > > releasing working again. > > > > > > > The release notes docs can always be updated/edit independent > from > > > > > > releases. > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Wed, Jan 7, 2026 at 9:13 AM Aurelien Pupier via dev < > > > > > > [email protected]> > > > > > > > wrote: > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > I think we should not change from which point the 4.17.0 > tag is > > > > > > created. > > > > > > > > I have in mind at least the change about deprecating olingo > > > > > components > > > > > > > > which won't be right as they are marked as deprecated since > 4.18 and > > > > > > there > > > > > > > > is an entry in the upgrade note to 4.18 > > > > > > > > ________________________________ > > > > > > > > From: Claus Ibsen <[email protected]> > > > > > > > > Sent: Wednesday, January 7, 2026 8:05 AM > > > > > > > > To: [email protected] <[email protected]> > > > > > > > > Subject: [EXTERNAL] Re: Camel 4.17.0 Release > > > > > > > > > > > > > > > > Hi > > > > > > > > > > > > > > > > The branches are GO for release. Good luck Gregor. > > > > > > > > > > > > > > > > On Wed, Jan 7, 2026 at 7:14 AM Claus Ibsen < > [email protected]> > > > > > > wrote: > > > > > > > > > > > > > > > > > Hi > > > > > > > > > > > > > > > > > > Gregor would like to try again releasing 4.17.0, but it > may be > > > > > > better to > > > > > > > > > use latest code from main, so we release from the top. > > > > > > > > > As he would need to redo the release from scratch. > > > > > > > > > > > > > > > > > > I am currently doing some validation of the code branches. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Tue, Jan 6, 2026 at 3:17 PM Gregor Zurowski < > > > > > > [email protected] > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > >> I have already deleted the duplicate repositories, and I > will > > > > > check > > > > > > > > >> the IP address on my next run. > > > > > > > > >> > > > > > > > > >> Thanks for your suggestion, it's much appreciated. > > > > > > > > >> > > > > > > > > >> On Tue, Jan 6, 2026 at 11:18 AM Aurélien Pupier < > > > > > [email protected] > > > > > > > > > > > > > > > >> wrote: > > > > > > > > >> > > > > > > > > > >> > I logged to the nexus and i see only 3 staging > repositories > > > > > > > > >> (orgapachecmale-1916, orgapachecamel-1942, > orgapachecamel1943), > > > > > not > > > > > > > > sure if > > > > > > > > >> it is that I do not have the correct rights of if the > "wrong ones" > > > > > > were > > > > > > > > >> already dropped. > > > > > > > > >> > > > > > > > > > >> > We can see the IP address detected on each staging > repository in > > > > > > the > > > > > > > > >> summary -> Owner. > > > > > > > > >> > I can notice that a different IP is mentioned for 2 of > the > > > > > > > > repositories > > > > > > > > >> you pushed (but given that they were created 5 days apart > that's > > > > > > sounds > > > > > > > > >> reasonable that you change of place or have a different IP > > > > > assigned) > > > > > > > > >> > > > > > > > > > >> > If you reproduce the multiple staging repository issue, > could > > > > > you > > > > > > > > check > > > > > > > > >> these IPs please? > > > > > > > > >> > > > > > > > > > >> > On 2026/01/06 10:10:54 Aurélien Pupier wrote: > > > > > > > > >> > > Hello, > > > > > > > > >> > > > > > > > > > > >> > > a slight stab in the dark but I found this old issue > > > > > mentioning > > > > > > > > >> duplicate staging repositories in case of Nexus thinking > that the > > > > > > > > artifacts > > > > > > > > >> are deployed from different IP > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > https://stackoverflow.com/questions/15511484/mvn-releaseperform-creates-multiple-staging-repos > > > > > > > > >> > > Is there by any chance that you are building from a > different > > > > > > place > > > > > > > > >> than before? Or a change in a proxy configuration that > you are > > > > > > using? > > > > > > > > >> > > > > > > > > > > >> > > On 2026/01/03 11:16:28 Gregor Zurowski wrote: > > > > > > > > >> > > > Hi, > > > > > > > > >> > > > > > > > > > > > >> > > > I am having issues building the Spring Boot project. > > > > > > Initially, > > > > > > > > >> there > > > > > > > > >> > > > were issues with the maven-release-plugin, which I > resolved > > > > > by > > > > > > > > >> > > > removing the overridden dependency on > > > > > > maven-scm-provider-gitexe. > > > > > > > > >> Next, > > > > > > > > >> > > > the release:prepare phase created two staging > repositories. > > > > > I > > > > > > > > tried > > > > > > > > >> it > > > > > > > > >> > > > twice with the same result. Then I reverted the > > > > > > > > maven-release-plugin > > > > > > > > >> > > > upgrade (back to version 2.4.0), but now the > release process > > > > > > > > creates > > > > > > > > >> > > > five staging repositories on every attempt. > > > > > > > > >> > > > > > > > > > > > >> > > > Any ideas on how to resolve this? > > > > > > > > >> > > > > > > > > > > > >> > > > Thanks, > > > > > > > > >> > > > Gregor > > > > > > > > >> > > > > > > > > > > > >> > > > On Sat, Jan 3, 2026 at 9:13 AM Claus Ibsen < > > > > > > [email protected] > > > > > > > > > > > > > > > > > >> wrote: > > > > > > > > >> > > > > > > > > > > > > >> > > > > Hi Gregor > > > > > > > > >> > > > > > > > > > > > > >> > > > > You may need to cherry pick this commit on > > > > > > camel-spring-boot for > > > > > > > > >> the 4.17.0 > > > > > > > > >> > > > > release branch > > > > > > > > >> > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > https://github.com/apache/camel-spring-boot/commit/3fa9afb02176f778c6c5d1d33107cd1f6f5ddb86 > > > > > > > > >> > > > > > > > > > > > > >> > > > > Though you would likely see that when building > 4.17.0 then > > > > > > you > > > > > > > > >> have changed > > > > > > > > >> > > > > source files that this commit included. > > > > > > > > >> > > > > > > > > > > > > >> > > > > On Thu, Jan 1, 2026 at 5:01 PM Claus Ibsen < > > > > > > > > [email protected]> > > > > > > > > >> wrote: > > > > > > > > >> > > > > > > > > > > > > >> > > > > > Hi Gregor > > > > > > > > >> > > > > > > > > > > > > > >> > > > > > Happy new year. > > > > > > > > >> > > > > > Yes you are welcome to start the 4.17.0 release. > > > > > > > > >> > > > > > > > > > > > > > >> > > > > > I have fixed RAT this morning and the code base > should > > > > > be > > > > > > > > okay. > > > > > > > > >> > > > > > > > > > > > > > >> > > > > > > > > > > > > > >> > > > > > > > > > > > > > >> > > > > > On Thu, Jan 1, 2026 at 3:44 PM Gregor Zurowski < > > > > > > > > >> [email protected]> > > > > > > > > >> > > > > > wrote: > > > > > > > > >> > > > > > > > > > > > > > >> > > > > >> Happy New Year, everyone! > > > > > > > > >> > > > > >> > > > > > > > > >> > > > > >> I started to work on the 4.17.0 release. > > > > > > > > >> > > > > >> > > > > > > > > >> > > > > >> On Sat, Dec 27, 2025 at 8:59 AM Claus Ibsen < > > > > > > > > >> [email protected]> > > > > > > > > >> > > > > >> wrote: > > > > > > > > >> > > > > >> > > > > > > > > > >> > > > > >> > Hi > > > > > > > > >> > > > > >> > > > > > > > > > >> > > > > >> > I got word from Gregor. We can do 4.17.0 > start of > > > > > 2026 > > > > > > and > > > > > > > > >> that is also > > > > > > > > >> > > > > >> > very good. > > > > > > > > >> > > > > >> > > > > > > > > > >> > > > > >> > > > > > > > > > >> > > > > >> > On Tue, Dec 23, 2025 at 9:04 AM Claus Ibsen < > > > > > > > > >> [email protected]> > > > > > > > > >> > > > > >> wrote: > > > > > > > > >> > > > > >> > > > > > > > > > >> > > > > >> > > Hi Gregor > > > > > > > > >> > > > > >> > > > > > > > > > > >> > > > > >> > > We can do the 4.17.0 release any time, if > you for > > > > > > example > > > > > > > > >> want to do > > > > > > > > >> > > > > >> it > > > > > > > > >> > > > > >> > > during this Christmas break. > > > > > > > > >> > > > > >> > > Just let us know and we plan accordingly. > > > > > > > > >> > > > > >> > > > > > > > > > > >> > > > > >> > > > > > > > > > > >> > > > > >> > > > > > > > > > > >> > > > > >> > > On Sun, Dec 7, 2025 at 10:00 AM Claus > Ibsen < > > > > > > > > >> [email protected]> > > > > > > > > >> > > > > >> wrote: > > > > > > > > >> > > > > >> > > > > > > > > > > >> > > > > >> > >> Hi > > > > > > > > >> > > > > >> > >> > > > > > > > > >> > > > > >> > >> It would be good to get a new release > after the > > > > > > patch > > > > > > > > >> release, or in > > > > > > > > >> > > > > >> the > > > > > > > > >> > > > > >> > >> first weeks of January. The 4.18 LTS is > planned > > > > > for > > > > > > > > >> February, when > > > > > > > > >> > > > > >> 4.10 LTS > > > > > > > > >> > > > > >> > >> expires. > > > > > > > > >> > > > > >> > >> > > > > > > > > >> > > > > >> > >> But at first its more important to get > the LTS > > > > > > patches > > > > > > > > >> released > > > > > > > > >> > > > > >> first. > > > > > > > > >> > > > > >> > >> > > > > > > > > >> > > > > >> > >> > > > > > > > > >> > > > > >> > >> > > > > > > > > >> > > > > >> > >> -- > > > > > > > > >> > > > > >> > >> Claus Ibsen > > > > > > > > >> > > > > >> > >> > > > > > > > > >> > > > > >> > > > > > > > > > > >> > > > > >> > > > > > > > > > > >> > > > > >> > > -- > > > > > > > > >> > > > > >> > > Claus Ibsen > > > > > > > > >> > > > > >> > > > > > > > > > > >> > > > > >> > > > > > > > > > >> > > > > >> > > > > > > > > > >> > > > > >> > -- > > > > > > > > >> > > > > >> > Claus Ibsen > > > > > > > > >> > > > > >> > > > > > > > > >> > > > > > > > > > > > > > >> > > > > > > > > > > > > > >> > > > > > -- > > > > > > > > >> > > > > > Claus Ibsen > > > > > > > > >> > > > > > > > > > > > > > >> > > > > > > > > > > > > >> > > > > > > > > > > > > >> > > > > -- > > > > > > > > >> > > > > Claus Ibsen > > > > > > > > >> > > > > > > > > > > > >> > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > Claus Ibsen > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > Claus Ibsen > > > > > > > > > > > > > > > > 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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Claus Ibsen > > > > > > > > > > > > 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 > > > > > > > > > > > > > > > > > > > > > -- > > > > > Claus Ibsen > > > > > > > > > > > > > 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 > -- Claus Ibsen
