Re: Camel 4.17.0 Release

[Gregor Zurowski <gr...@list.zurowski.org>]

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 <cl...@gmail.com> 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 <cl...@gmail.com> 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 <cl...@gmail.com> 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

RE: Camel 4.17.0 Release

[Aurelien Pupier via dev <de...@camel.apache.org>]

But the change I mention is on Camel core only. Is it only Camel spring boot which which is affected by this change of tag position?
________________________________
From: Aurelien Pupier <ap...@ibm.com>
Sent: Wednesday, January 7, 2026 9:13 AM
To: dev@camel.apache.org <de...@camel.apache.org>
Subject: Re: [EXTERNAL] Re: Camel 4.17.0 Release

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 <cl...@gmail.com>
Sent: Wednesday, January 7, 2026 8:05 AM
To: dev@camel.apache.org <de...@camel.apache.org>
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 <cl...@gmail.com> 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 <gr...@list.zurowski.org>
> 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 <ap...@apache.org>
>> 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 <cl...@gmail.com>
>> 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 <cl...@gmail.com>
>> 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 <
>> gregor@list.zurowski.org>
>> > > > > > 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 <
>> claus.ibsen@gmail.com>
>> > > > > >> 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 <
>> claus.ibsen@gmail.com>
>> > > > > >> 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 <
>> claus.ibsen@gmail.com>
>> > > > > >> 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

Re: Camel 4.17.0 Release

[Gregor Zurowski <gr...@list.zurowski.org>]

I will try a couple of tweaks and follow up shortly.

On Wed, Jan 7, 2026 at 11:08 AM Andrea Cosentino <an...@gmail.com> wrote:
>
> Maybe we should look at moving to nexus-maven-plugin?
>
> Il giorno mer 7 gen 2026 alle ore 10:54 Gregor Zurowski <
> gregor@list.zurowski.org> ha scritto:
>
> > 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 <cl...@gmail.com> 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 <
> > dev@camel.apache.org>
> > > 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 <cl...@gmail.com>
> > > > Sent: Wednesday, January 7, 2026 8:05 AM
> > > > To: dev@camel.apache.org <de...@camel.apache.org>
> > > > 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 <cl...@gmail.com>
> > 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 <
> > gregor@list.zurowski.org
> > > > >
> > > > > 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 <apupier@apache.org
> > >
> > > > >> 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 <
> > claus.ibsen@gmail.com
> > > > >
> > > > >> 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 <
> > > > claus.ibsen@gmail.com>
> > > > >> 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 <
> > > > >> gregor@list.zurowski.org>
> > > > >> > > > > > 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 <
> > > > >> claus.ibsen@gmail.com>
> > > > >> > > > > >> 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 <
> > > > >> claus.ibsen@gmail.com>
> > > > >> > > > > >> 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 <
> > > > >> claus.ibsen@gmail.com>
> > > > >> > > > > >> 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
> >

Re: Camel 4.17.0 Release

[Andrea Cosentino <an...@gmail.com>]

Maybe we should look at moving to nexus-maven-plugin?

Il giorno mer 7 gen 2026 alle ore 10:54 Gregor Zurowski <
gregor@list.zurowski.org> ha scritto:

> 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 <cl...@gmail.com> 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 <
> dev@camel.apache.org>
> > 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 <cl...@gmail.com>
> > > Sent: Wednesday, January 7, 2026 8:05 AM
> > > To: dev@camel.apache.org <de...@camel.apache.org>
> > > 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 <cl...@gmail.com>
> 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 <
> gregor@list.zurowski.org
> > > >
> > > > 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 <apupier@apache.org
> >
> > > >> 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 <
> claus.ibsen@gmail.com
> > > >
> > > >> 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 <
> > > claus.ibsen@gmail.com>
> > > >> 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 <
> > > >> gregor@list.zurowski.org>
> > > >> > > > > > 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 <
> > > >> claus.ibsen@gmail.com>
> > > >> > > > > >> 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 <
> > > >> claus.ibsen@gmail.com>
> > > >> > > > > >> 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 <
> > > >> claus.ibsen@gmail.com>
> > > >> > > > > >> 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
>

Re: Camel 4.17.0 Release

[Aurélien Pupier <ap...@apache.org>]

Hi,

and big thanks to you Gregor for leading the effort of these community releases, even when they came with some challenges!

On 2026/01/09 09:11:12 Gregor Zurowski wrote:
> Hi Everyone:
> 
> After countless builds and release attempts, I finally sent out the
> vote email for Camel 4.17.0. I wanted to thank everyone for your help
> and support throughout the process! This has been an amazing
> collaboration and team effort. Thank you!
> 
> Gregor
> 
> On Thu, Jan 8, 2026 at 12:27 PM Claus Ibsen <cl...@gmail.com> wrote:
> >
> > 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 <gr...@list.zurowski.org>
> > 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
> > > <de...@camel.apache.org> 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 <gr...@list.zurowski.org>
> > > > Sent: Thursday, January 8, 2026 9:34 AM
> > > > To: dev@camel.apache.org <de...@camel.apache.org>
> > > > 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 <ap...@apache.org>
> > > 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 <cl...@gmail.com>
> > > 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 <
> > > > > > > dev@camel.apache.org> 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 <gr...@list.zurowski.org>
> > > > > > > > Sent: Wednesday, January 7, 2026 10:54 AM
> > > > > > > > To: dev@camel.apache.org <de...@camel.apache.org>
> > > > > > > > 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 <
> > > claus.ibsen@gmail.com>
> > > > > > > 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 <
> > > > > > > > dev@camel.apache.org>
> > > > > > > > > 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 <cl...@gmail.com>
> > > > > > > > > > Sent: Wednesday, January 7, 2026 8:05 AM
> > > > > > > > > > To: dev@camel.apache.org <de...@camel.apache.org>
> > > > > > > > > > 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 <
> > > claus.ibsen@gmail.com>
> > > > > > > > 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 <
> > > > > > > > gregor@list.zurowski.org
> > > > > > > > > > >
> > > > > > > > > > > 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 <
> > > > > > > apupier@apache.org
> > > > > > > > >
> > > > > > > > > > >> 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 <
> > > > > > > > claus.ibsen@gmail.com
> > > > > > > > > > >
> > > > > > > > > > >> 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 <
> > > > > > > > > > claus.ibsen@gmail.com>
> > > > > > > > > > >> 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 <
> > > > > > > > > > >> gregor@list.zurowski.org>
> > > > > > > > > > >> > > > > > 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 <
> > > > > > > > > > >> claus.ibsen@gmail.com>
> > > > > > > > > > >> > > > > >> 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 <
> > > > > > > > > > >> claus.ibsen@gmail.com>
> > > > > > > > > > >> > > > > >> 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 <
> > > > > > > > > > >> claus.ibsen@gmail.com>
> > > > > > > > > > >> > > > > >> 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
> 

Re: Camel 4.17.0 Release

[Claus Ibsen <cl...@gmail.com>]

Hi

Thank you everyone. I agree its great when people step up and help, so the
burden does not fall on Gregor alone.
It's tough to keep using spare time to do releases, and even so when you do
not directly need to use a new Camel version.

We should be glad that we can keep the wheels spinning for Apache Camel and
keep driving out new releases and patch releases for the world to use.
And that there is still a healthy balance between community contributors
and users / and commercial companies that can sponsor paid work.

So we are on track again for Camel 4.18 LTS.



On Fri, Jan 9, 2026 at 10:12 AM Gregor Zurowski <gr...@list.zurowski.org>
wrote:

> Hi Everyone:
>
> After countless builds and release attempts, I finally sent out the
> vote email for Camel 4.17.0. I wanted to thank everyone for your help
> and support throughout the process! This has been an amazing
> collaboration and team effort. Thank you!
>
> Gregor
>
> On Thu, Jan 8, 2026 at 12:27 PM Claus Ibsen <cl...@gmail.com> wrote:
> >
> > 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 <
> gregor@list.zurowski.org>
> > 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
> > > <de...@camel.apache.org> 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 <gr...@list.zurowski.org>
> > > > Sent: Thursday, January 8, 2026 9:34 AM
> > > > To: dev@camel.apache.org <de...@camel.apache.org>
> > > > 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 <ap...@apache.org>
> > > 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 <
> claus.ibsen@gmail.com>
> > > 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 <
> > > > > > > dev@camel.apache.org> 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 <gr...@list.zurowski.org>
> > > > > > > > Sent: Wednesday, January 7, 2026 10:54 AM
> > > > > > > > To: dev@camel.apache.org <de...@camel.apache.org>
> > > > > > > > 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 <
> > > claus.ibsen@gmail.com>
> > > > > > > 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 <
> > > > > > > > dev@camel.apache.org>
> > > > > > > > > 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 <cl...@gmail.com>
> > > > > > > > > > Sent: Wednesday, January 7, 2026 8:05 AM
> > > > > > > > > > To: dev@camel.apache.org <de...@camel.apache.org>
> > > > > > > > > > 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 <
> > > claus.ibsen@gmail.com>
> > > > > > > > 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 <
> > > > > > > > gregor@list.zurowski.org
> > > > > > > > > > >
> > > > > > > > > > > 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 <
> > > > > > > apupier@apache.org
> > > > > > > > >
> > > > > > > > > > >> 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 <
> > > > > > > > claus.ibsen@gmail.com
> > > > > > > > > > >
> > > > > > > > > > >> 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 <
> > > > > > > > > > claus.ibsen@gmail.com>
> > > > > > > > > > >> 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 <
> > > > > > > > > > >> gregor@list.zurowski.org>
> > > > > > > > > > >> > > > > > 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 <
> > > > > > > > > > >> claus.ibsen@gmail.com>
> > > > > > > > > > >> > > > > >> 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 <
> > > > > > > > > > >> claus.ibsen@gmail.com>
> > > > > > > > > > >> > > > > >> 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 <
> > > > > > > > > > >> claus.ibsen@gmail.com>
> > > > > > > > > > >> > > > > >> 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
>


-- 
Claus Ibsen

Re: Camel 4.17.0 Release

[Gregor Zurowski <gr...@list.zurowski.org>]

Hi Everyone:

After countless builds and release attempts, I finally sent out the
vote email for Camel 4.17.0. I wanted to thank everyone for your help
and support throughout the process! This has been an amazing
collaboration and team effort. Thank you!

Gregor

On Thu, Jan 8, 2026 at 12:27 PM Claus Ibsen <cl...@gmail.com> wrote:
>
> 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 <gr...@list.zurowski.org>
> 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
> > <de...@camel.apache.org> 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 <gr...@list.zurowski.org>
> > > Sent: Thursday, January 8, 2026 9:34 AM
> > > To: dev@camel.apache.org <de...@camel.apache.org>
> > > 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 <ap...@apache.org>
> > 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 <cl...@gmail.com>
> > 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 <
> > > > > > dev@camel.apache.org> 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 <gr...@list.zurowski.org>
> > > > > > > Sent: Wednesday, January 7, 2026 10:54 AM
> > > > > > > To: dev@camel.apache.org <de...@camel.apache.org>
> > > > > > > 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 <
> > claus.ibsen@gmail.com>
> > > > > > 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 <
> > > > > > > dev@camel.apache.org>
> > > > > > > > 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 <cl...@gmail.com>
> > > > > > > > > Sent: Wednesday, January 7, 2026 8:05 AM
> > > > > > > > > To: dev@camel.apache.org <de...@camel.apache.org>
> > > > > > > > > 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 <
> > claus.ibsen@gmail.com>
> > > > > > > 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 <
> > > > > > > gregor@list.zurowski.org
> > > > > > > > > >
> > > > > > > > > > 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 <
> > > > > > apupier@apache.org
> > > > > > > >
> > > > > > > > > >> 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 <
> > > > > > > claus.ibsen@gmail.com
> > > > > > > > > >
> > > > > > > > > >> 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 <
> > > > > > > > > claus.ibsen@gmail.com>
> > > > > > > > > >> 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 <
> > > > > > > > > >> gregor@list.zurowski.org>
> > > > > > > > > >> > > > > > 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 <
> > > > > > > > > >> claus.ibsen@gmail.com>
> > > > > > > > > >> > > > > >> 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 <
> > > > > > > > > >> claus.ibsen@gmail.com>
> > > > > > > > > >> > > > > >> 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 <
> > > > > > > > > >> claus.ibsen@gmail.com>
> > > > > > > > > >> > > > > >> 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

Re: Camel 4.17.0 Release

[Claus Ibsen <cl...@gmail.com>]

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 <gr...@list.zurowski.org>
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
> <de...@camel.apache.org> 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 <gr...@list.zurowski.org>
> > Sent: Thursday, January 8, 2026 9:34 AM
> > To: dev@camel.apache.org <de...@camel.apache.org>
> > 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 <ap...@apache.org>
> 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 <cl...@gmail.com>
> 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 <
> > > > > dev@camel.apache.org> 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 <gr...@list.zurowski.org>
> > > > > > Sent: Wednesday, January 7, 2026 10:54 AM
> > > > > > To: dev@camel.apache.org <de...@camel.apache.org>
> > > > > > 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 <
> claus.ibsen@gmail.com>
> > > > > 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 <
> > > > > > dev@camel.apache.org>
> > > > > > > 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 <cl...@gmail.com>
> > > > > > > > Sent: Wednesday, January 7, 2026 8:05 AM
> > > > > > > > To: dev@camel.apache.org <de...@camel.apache.org>
> > > > > > > > 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 <
> claus.ibsen@gmail.com>
> > > > > > 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 <
> > > > > > gregor@list.zurowski.org
> > > > > > > > >
> > > > > > > > > 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 <
> > > > > apupier@apache.org
> > > > > > >
> > > > > > > > >> 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 <
> > > > > > claus.ibsen@gmail.com
> > > > > > > > >
> > > > > > > > >> 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 <
> > > > > > > > claus.ibsen@gmail.com>
> > > > > > > > >> 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 <
> > > > > > > > >> gregor@list.zurowski.org>
> > > > > > > > >> > > > > > 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 <
> > > > > > > > >> claus.ibsen@gmail.com>
> > > > > > > > >> > > > > >> 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 <
> > > > > > > > >> claus.ibsen@gmail.com>
> > > > > > > > >> > > > > >> 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 <
> > > > > > > > >> claus.ibsen@gmail.com>
> > > > > > > > >> > > > > >> 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

Re: Camel 4.17.0 Release

[Gregor Zurowski <gr...@list.zurowski.org>]

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
<de...@camel.apache.org> 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 <gr...@list.zurowski.org>
> Sent: Thursday, January 8, 2026 9:34 AM
> To: dev@camel.apache.org <de...@camel.apache.org>
> 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 <ap...@apache.org> 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 <cl...@gmail.com> 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 <
> > > > dev@camel.apache.org> 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 <gr...@list.zurowski.org>
> > > > > Sent: Wednesday, January 7, 2026 10:54 AM
> > > > > To: dev@camel.apache.org <de...@camel.apache.org>
> > > > > 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 <cl...@gmail.com>
> > > > 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 <
> > > > > dev@camel.apache.org>
> > > > > > 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 <cl...@gmail.com>
> > > > > > > Sent: Wednesday, January 7, 2026 8:05 AM
> > > > > > > To: dev@camel.apache.org <de...@camel.apache.org>
> > > > > > > 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 <cl...@gmail.com>
> > > > > 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 <
> > > > > gregor@list.zurowski.org
> > > > > > > >
> > > > > > > > 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 <
> > > > apupier@apache.org
> > > > > >
> > > > > > > >> 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 <
> > > > > claus.ibsen@gmail.com
> > > > > > > >
> > > > > > > >> 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 <
> > > > > > > claus.ibsen@gmail.com>
> > > > > > > >> 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 <
> > > > > > > >> gregor@list.zurowski.org>
> > > > > > > >> > > > > > 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 <
> > > > > > > >> claus.ibsen@gmail.com>
> > > > > > > >> > > > > >> 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 <
> > > > > > > >> claus.ibsen@gmail.com>
> > > > > > > >> > > > > >> 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 <
> > > > > > > >> claus.ibsen@gmail.com>
> > > > > > > >> > > > > >> 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

RE: Camel 4.17.0 Release

[Aurelien Pupier via dev <de...@camel.apache.org>]

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 <gr...@list.zurowski.org>
Sent: Thursday, January 8, 2026 9:34 AM
To: dev@camel.apache.org <de...@camel.apache.org>
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 <ap...@apache.org> 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 <cl...@gmail.com> 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 <
> > > dev@camel.apache.org> 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 <gr...@list.zurowski.org>
> > > > Sent: Wednesday, January 7, 2026 10:54 AM
> > > > To: dev@camel.apache.org <de...@camel.apache.org>
> > > > 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 <cl...@gmail.com>
> > > 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 <
> > > > dev@camel.apache.org>
> > > > > 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 <cl...@gmail.com>
> > > > > > Sent: Wednesday, January 7, 2026 8:05 AM
> > > > > > To: dev@camel.apache.org <de...@camel.apache.org>
> > > > > > 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 <cl...@gmail.com>
> > > > 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 <
> > > > gregor@list.zurowski.org
> > > > > > >
> > > > > > > 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 <
> > > apupier@apache.org
> > > > >
> > > > > > >> 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 <
> > > > claus.ibsen@gmail.com
> > > > > > >
> > > > > > >> 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 <
> > > > > > claus.ibsen@gmail.com>
> > > > > > >> 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 <
> > > > > > >> gregor@list.zurowski.org>
> > > > > > >> > > > > > 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 <
> > > > > > >> claus.ibsen@gmail.com>
> > > > > > >> > > > > >> 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 <
> > > > > > >> claus.ibsen@gmail.com>
> > > > > > >> > > > > >> 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 <
> > > > > > >> claus.ibsen@gmail.com>
> > > > > > >> > > > > >> 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

Re: Camel 4.17.0 Release

[Gregor Zurowski <gr...@list.zurowski.org>]

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 <ap...@apache.org> 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 <cl...@gmail.com> 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 <
> > > dev@camel.apache.org> 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 <gr...@list.zurowski.org>
> > > > Sent: Wednesday, January 7, 2026 10:54 AM
> > > > To: dev@camel.apache.org <de...@camel.apache.org>
> > > > 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 <cl...@gmail.com>
> > > 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 <
> > > > dev@camel.apache.org>
> > > > > 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 <cl...@gmail.com>
> > > > > > Sent: Wednesday, January 7, 2026 8:05 AM
> > > > > > To: dev@camel.apache.org <de...@camel.apache.org>
> > > > > > 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 <cl...@gmail.com>
> > > > 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 <
> > > > gregor@list.zurowski.org
> > > > > > >
> > > > > > > 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 <
> > > apupier@apache.org
> > > > >
> > > > > > >> 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 <
> > > > claus.ibsen@gmail.com
> > > > > > >
> > > > > > >> 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 <
> > > > > > claus.ibsen@gmail.com>
> > > > > > >> 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 <
> > > > > > >> gregor@list.zurowski.org>
> > > > > > >> > > > > > 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 <
> > > > > > >> claus.ibsen@gmail.com>
> > > > > > >> > > > > >> 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 <
> > > > > > >> claus.ibsen@gmail.com>
> > > > > > >> > > > > >> 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 <
> > > > > > >> claus.ibsen@gmail.com>
> > > > > > >> > > > > >> 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
> > >
> >

Re: Camel 4.17.0 Release

[Aurélien Pupier <ap...@apache.org>]

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 <cl...@gmail.com> 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 <
> > dev@camel.apache.org> 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 <gr...@list.zurowski.org>
> > > Sent: Wednesday, January 7, 2026 10:54 AM
> > > To: dev@camel.apache.org <de...@camel.apache.org>
> > > 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 <cl...@gmail.com>
> > 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 <
> > > dev@camel.apache.org>
> > > > 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 <cl...@gmail.com>
> > > > > Sent: Wednesday, January 7, 2026 8:05 AM
> > > > > To: dev@camel.apache.org <de...@camel.apache.org>
> > > > > 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 <cl...@gmail.com>
> > > 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 <
> > > gregor@list.zurowski.org
> > > > > >
> > > > > > 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 <
> > apupier@apache.org
> > > >
> > > > > >> 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 <
> > > claus.ibsen@gmail.com
> > > > > >
> > > > > >> 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 <
> > > > > claus.ibsen@gmail.com>
> > > > > >> 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 <
> > > > > >> gregor@list.zurowski.org>
> > > > > >> > > > > > 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 <
> > > > > >> claus.ibsen@gmail.com>
> > > > > >> > > > > >> 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 <
> > > > > >> claus.ibsen@gmail.com>
> > > > > >> > > > > >> 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 <
> > > > > >> claus.ibsen@gmail.com>
> > > > > >> > > > > >> 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
> >
> 

Re: Camel 4.17.0 Release

[Aurélien Pupier <ap...@redhat.com>]

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 <cl...@gmail.com> 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 <
> dev@camel.apache.org> 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 <gr...@list.zurowski.org>
> > Sent: Wednesday, January 7, 2026 10:54 AM
> > To: dev@camel.apache.org <de...@camel.apache.org>
> > 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 <cl...@gmail.com>
> 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 <
> > dev@camel.apache.org>
> > > 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 <cl...@gmail.com>
> > > > Sent: Wednesday, January 7, 2026 8:05 AM
> > > > To: dev@camel.apache.org <de...@camel.apache.org>
> > > > 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 <cl...@gmail.com>
> > 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 <
> > gregor@list.zurowski.org
> > > > >
> > > > > 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 <
> apupier@apache.org
> > >
> > > > >> 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 <
> > claus.ibsen@gmail.com
> > > > >
> > > > >> 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 <
> > > > claus.ibsen@gmail.com>
> > > > >> 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 <
> > > > >> gregor@list.zurowski.org>
> > > > >> > > > > > 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 <
> > > > >> claus.ibsen@gmail.com>
> > > > >> > > > > >> 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 <
> > > > >> claus.ibsen@gmail.com>
> > > > >> > > > > >> 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 <
> > > > >> claus.ibsen@gmail.com>
> > > > >> > > > > >> 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
>

Re: Camel 4.17.0 Release

[Claus Ibsen <cl...@gmail.com>]

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 <
dev@camel.apache.org> 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 <gr...@list.zurowski.org>
> Sent: Wednesday, January 7, 2026 10:54 AM
> To: dev@camel.apache.org <de...@camel.apache.org>
> 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 <cl...@gmail.com> 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 <
> dev@camel.apache.org>
> > 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 <cl...@gmail.com>
> > > Sent: Wednesday, January 7, 2026 8:05 AM
> > > To: dev@camel.apache.org <de...@camel.apache.org>
> > > 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 <cl...@gmail.com>
> 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 <
> gregor@list.zurowski.org
> > > >
> > > > 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 <apupier@apache.org
> >
> > > >> 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 <
> claus.ibsen@gmail.com
> > > >
> > > >> 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 <
> > > claus.ibsen@gmail.com>
> > > >> 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 <
> > > >> gregor@list.zurowski.org>
> > > >> > > > > > 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 <
> > > >> claus.ibsen@gmail.com>
> > > >> > > > > >> 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 <
> > > >> claus.ibsen@gmail.com>
> > > >> > > > > >> 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 <
> > > >> claus.ibsen@gmail.com>
> > > >> > > > > >> 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

RE: Camel 4.17.0 Release

[Aurelien Pupier via dev <de...@camel.apache.org>]

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 <gr...@list.zurowski.org>
Sent: Wednesday, January 7, 2026 10:54 AM
To: dev@camel.apache.org <de...@camel.apache.org>
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 <cl...@gmail.com> 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 <de...@camel.apache.org>
> 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 <cl...@gmail.com>
> > Sent: Wednesday, January 7, 2026 8:05 AM
> > To: dev@camel.apache.org <de...@camel.apache.org>
> > 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 <cl...@gmail.com> 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 <gregor@list.zurowski.org
> > >
> > > 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 <ap...@apache.org>
> > >> 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 <claus.ibsen@gmail.com
> > >
> > >> 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 <
> > claus.ibsen@gmail.com>
> > >> 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 <
> > >> gregor@list.zurowski.org>
> > >> > > > > > 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 <
> > >> claus.ibsen@gmail.com>
> > >> > > > > >> 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 <
> > >> claus.ibsen@gmail.com>
> > >> > > > > >> 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 <
> > >> claus.ibsen@gmail.com>
> > >> > > > > >> 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

Re: Camel 4.17.0 Release

[Gregor Zurowski <gr...@list.zurowski.org>]

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 <cl...@gmail.com> 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 <de...@camel.apache.org>
> 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 <cl...@gmail.com>
> > Sent: Wednesday, January 7, 2026 8:05 AM
> > To: dev@camel.apache.org <de...@camel.apache.org>
> > 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 <cl...@gmail.com> 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 <gregor@list.zurowski.org
> > >
> > > 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 <ap...@apache.org>
> > >> 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 <claus.ibsen@gmail.com
> > >
> > >> 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 <
> > claus.ibsen@gmail.com>
> > >> 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 <
> > >> gregor@list.zurowski.org>
> > >> > > > > > 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 <
> > >> claus.ibsen@gmail.com>
> > >> > > > > >> 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 <
> > >> claus.ibsen@gmail.com>
> > >> > > > > >> 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 <
> > >> claus.ibsen@gmail.com>
> > >> > > > > >> 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

Re: Camel 4.17.0 Release

[Claus Ibsen <cl...@gmail.com>]

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 <de...@camel.apache.org>
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 <cl...@gmail.com>
> Sent: Wednesday, January 7, 2026 8:05 AM
> To: dev@camel.apache.org <de...@camel.apache.org>
> 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 <cl...@gmail.com> 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 <gregor@list.zurowski.org
> >
> > 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 <ap...@apache.org>
> >> 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 <claus.ibsen@gmail.com
> >
> >> 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 <
> claus.ibsen@gmail.com>
> >> 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 <
> >> gregor@list.zurowski.org>
> >> > > > > > 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 <
> >> claus.ibsen@gmail.com>
> >> > > > > >> 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 <
> >> claus.ibsen@gmail.com>
> >> > > > > >> 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 <
> >> claus.ibsen@gmail.com>
> >> > > > > >> 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

RE: Camel 4.17.0 Release

[Aurelien Pupier via dev <de...@camel.apache.org>]

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 <cl...@gmail.com>
Sent: Wednesday, January 7, 2026 8:05 AM
To: dev@camel.apache.org <de...@camel.apache.org>
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 <cl...@gmail.com> 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 <gr...@list.zurowski.org>
> 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 <ap...@apache.org>
>> 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 <cl...@gmail.com>
>> 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 <cl...@gmail.com>
>> 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 <
>> gregor@list.zurowski.org>
>> > > > > > 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 <
>> claus.ibsen@gmail.com>
>> > > > > >> 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 <
>> claus.ibsen@gmail.com>
>> > > > > >> 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 <
>> claus.ibsen@gmail.com>
>> > > > > >> 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

Re: Camel 4.17.0 Release

[Claus Ibsen <cl...@gmail.com>]

Hi

The branches are GO for release. Good luck Gregor.

On Wed, Jan 7, 2026 at 7:14 AM Claus Ibsen <cl...@gmail.com> 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 <gr...@list.zurowski.org>
> 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 <ap...@apache.org>
>> 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 <cl...@gmail.com>
>> 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 <cl...@gmail.com>
>> 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 <
>> gregor@list.zurowski.org>
>> > > > > > 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 <
>> claus.ibsen@gmail.com>
>> > > > > >> 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 <
>> claus.ibsen@gmail.com>
>> > > > > >> 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 <
>> claus.ibsen@gmail.com>
>> > > > > >> 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

Re: Camel 4.17.0 Release

[Claus Ibsen <cl...@gmail.com>]

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 <gr...@list.zurowski.org>
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 <ap...@apache.org>
> 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 <cl...@gmail.com>
> 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 <cl...@gmail.com>
> 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 <
> gregor@list.zurowski.org>
> > > > > > 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 <
> claus.ibsen@gmail.com>
> > > > > >> 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 <
> claus.ibsen@gmail.com>
> > > > > >> 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 <
> claus.ibsen@gmail.com>
> > > > > >> 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

Re: Camel 4.17.0 Release

[Gregor Zurowski <gr...@list.zurowski.org>]

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 <ap...@apache.org> 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 <cl...@gmail.com> 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 <cl...@gmail.com> 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 <gr...@list.zurowski.org>
> > > > > 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 <cl...@gmail.com>
> > > > >> 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 <cl...@gmail.com>
> > > > >> 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 <cl...@gmail.com>
> > > > >> 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
> > >
> >

Re: Camel 4.17.0 Release

[Aurélien Pupier <ap...@apache.org>]

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 <cl...@gmail.com> 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 <cl...@gmail.com> 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 <gr...@list.zurowski.org>
> > > > 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 <cl...@gmail.com>
> > > >> 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 <cl...@gmail.com>
> > > >> 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 <cl...@gmail.com>
> > > >> 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
> > 
> 

Re: Camel 4.17.0 Release

[Aurélien Pupier <ap...@apache.org>]

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 <cl...@gmail.com> 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 <cl...@gmail.com> 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 <gr...@list.zurowski.org>
> > > 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 <cl...@gmail.com>
> > >> 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 <cl...@gmail.com>
> > >> 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 <cl...@gmail.com>
> > >> 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
> 

Re: Camel 4.17.0 Release

[Claus Ibsen <cl...@gmail.com>]

Hi

Also maybe camel-spring-boot uses some of the versions defined in
camel-core project, and the diff to 4.16.0 has a few that was upraded in
root pom.xml

-
 <project.build.outputTimestamp>2025-11-01T09:08:46Z</project.build.outputTimestamp>
+
 <project.build.outputTimestamp>2026-01-01T15:49:55Z</project.build.outputTimestamp>


 <cyclonedx-maven-plugin-version>2.9.1</cyclonedx-maven-plugin-version>
         <flatten-maven-plugin-version>1.7.3</flatten-maven-plugin-version>
         <gmavenplus-plugin-version>2.1.0</gmavenplus-plugin-version>
         <license-maven-plugin-version>5.0.0</license-maven-plugin-version>
-
 <maven-assembly-plugin-version>3.7.1</maven-assembly-plugin-version>
+
 <maven-assembly-plugin-version>3.8.0</maven-assembly-plugin-version>

 <maven-compiler-plugin-version>3.14.1</maven-compiler-plugin-version>

 <maven-dependency-plugin-version>3.9.0</maven-dependency-plugin-version>

 <maven-enforcer-plugin-version>3.6.2</maven-enforcer-plugin-version>
         <maven-invoker-plugin-version>3.9.1</maven-invoker-plugin-version>
         <maven-javadoc-plugin-version>3.12.0</maven-javadoc-plugin-version>
-        <maven-release-plugin-version>3.1.1</maven-release-plugin-version>
+        <maven-release-plugin-version>3.3.1</maven-release-plugin-version>

 <maven-remote-resources-plugin-version>3.3.0</maven-remote-resources-plugin-version>

 <maven-surefire-plugin-version>3.5.4</maven-surefire-plugin-version>

 <templating-maven-plugin-version>3.0.0</templating-maven-plugin-version>
-
 <versions-maven-plugin-version>2.19.1</versions-maven-plugin-version>
+
 <versions-maven-plugin-version>2.20.1</versions-maven-plugin-version>


On Sat, Jan 3, 2026 at 1:16 PM Claus Ibsen <cl...@gmail.com> wrote:

> Hi
>
> Also a little diff is in parent/pom.xml that the maven-jar-plugin is 3.4.2
> vs 3.5.0 comparing to the 4.16.0 release.
>
> On Sat, Jan 3, 2026 at 1:13 PM Claus Ibsen <cl...@gmail.com> wrote:
>
>> Hi Gregor
>>
>> Ah its not good to hear yet another releasing problem.
>> Comparing the pom.xml with 4.16.0 then with the revert of the release
>> maven plugin then those 2 files looks similar and there is no hint that
>> this causes the problem.
>>
>> Asking grok tells of others having this kind of 2+ staging repos being
>> created. And it seems switching to another maven plugin may resolve this
>> https://grok.com/share/c2hhcmQtMw_291cbde9-676b-4ddb-baad-f27a859929e9
>>
>> I wonder if we have this problem on older branches like 4.14.x or 4.10.x.
>> Or that its only main branch. ie its a new problem.
>> We could try to build and release 4.14.4 and see if also has that problem.
>>
>> And we can then look at other ASF projects if they use nexus-staging-maven-plugin
>> and see how they do it.
>> And try to use this in the future.
>>
>>
>>
>>
>>
>>
>>
>> On Sat, Jan 3, 2026 at 12:17 PM Gregor Zurowski <gr...@list.zurowski.org>
>> 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 <cl...@gmail.com>
>>> 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 <cl...@gmail.com>
>>> 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 <
>>> gregor@list.zurowski.org>
>>> > > 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 <cl...@gmail.com>
>>> > >> 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 <
>>> claus.ibsen@gmail.com>
>>> > >> 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 <
>>> claus.ibsen@gmail.com>
>>> > >> 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
>


-- 
Claus Ibsen

Re: Camel 4.17.0 Release

[Claus Ibsen <cl...@gmail.com>]

Hi

Also a little diff is in parent/pom.xml that the maven-jar-plugin is 3.4.2
vs 3.5.0 comparing to the 4.16.0 release.

On Sat, Jan 3, 2026 at 1:13 PM Claus Ibsen <cl...@gmail.com> wrote:

> Hi Gregor
>
> Ah its not good to hear yet another releasing problem.
> Comparing the pom.xml with 4.16.0 then with the revert of the release
> maven plugin then those 2 files looks similar and there is no hint that
> this causes the problem.
>
> Asking grok tells of others having this kind of 2+ staging repos being
> created. And it seems switching to another maven plugin may resolve this
> https://grok.com/share/c2hhcmQtMw_291cbde9-676b-4ddb-baad-f27a859929e9
>
> I wonder if we have this problem on older branches like 4.14.x or 4.10.x.
> Or that its only main branch. ie its a new problem.
> We could try to build and release 4.14.4 and see if also has that problem.
>
> And we can then look at other ASF projects if they use nexus-staging-maven-plugin
> and see how they do it.
> And try to use this in the future.
>
>
>
>
>
>
>
> On Sat, Jan 3, 2026 at 12:17 PM Gregor Zurowski <gr...@list.zurowski.org>
> 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 <cl...@gmail.com> 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 <cl...@gmail.com>
>> 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 <
>> gregor@list.zurowski.org>
>> > > 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 <cl...@gmail.com>
>> > >> 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 <claus.ibsen@gmail.com
>> >
>> > >> 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 <
>> claus.ibsen@gmail.com>
>> > >> 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

Re: Camel 4.17.0 Release

[Claus Ibsen <cl...@gmail.com>]

Hi

Apache Nifi is using nexus-staging-plugin
https://github.com/apache/nifi-maven/blob/main/pom.xml

And reading their docs it seems its a maven extension to replace 1 to 1 the
maven-release-plugin (which happens automatic)
https://github.com/sonatype/nexus-maven-plugins/blob/main/staging/maven-plugin/README.md




On Sat, Jan 3, 2026 at 1:13 PM Claus Ibsen <cl...@gmail.com> wrote:

> Hi Gregor
>
> Ah its not good to hear yet another releasing problem.
> Comparing the pom.xml with 4.16.0 then with the revert of the release
> maven plugin then those 2 files looks similar and there is no hint that
> this causes the problem.
>
> Asking grok tells of others having this kind of 2+ staging repos being
> created. And it seems switching to another maven plugin may resolve this
> https://grok.com/share/c2hhcmQtMw_291cbde9-676b-4ddb-baad-f27a859929e9
>
> I wonder if we have this problem on older branches like 4.14.x or 4.10.x.
> Or that its only main branch. ie its a new problem.
> We could try to build and release 4.14.4 and see if also has that problem.
>
> And we can then look at other ASF projects if they use nexus-staging-maven-plugin
> and see how they do it.
> And try to use this in the future.
>
>
>
>
>
>
>
> On Sat, Jan 3, 2026 at 12:17 PM Gregor Zurowski <gr...@list.zurowski.org>
> 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 <cl...@gmail.com> 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 <cl...@gmail.com>
>> 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 <
>> gregor@list.zurowski.org>
>> > > 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 <cl...@gmail.com>
>> > >> 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 <claus.ibsen@gmail.com
>> >
>> > >> 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 <
>> claus.ibsen@gmail.com>
>> > >> 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

Re: Camel 4.17.0 Release

[Claus Ibsen <cl...@gmail.com>]

Hi Gregor

Ah its not good to hear yet another releasing problem.
Comparing the pom.xml with 4.16.0 then with the revert of the release maven
plugin then those 2 files looks similar and there is no hint that this
causes the problem.

Asking grok tells of others having this kind of 2+ staging repos being
created. And it seems switching to another maven plugin may resolve this
https://grok.com/share/c2hhcmQtMw_291cbde9-676b-4ddb-baad-f27a859929e9

I wonder if we have this problem on older branches like 4.14.x or 4.10.x.
Or that its only main branch. ie its a new problem.
We could try to build and release 4.14.4 and see if also has that problem.

And we can then look at other ASF projects if they use
nexus-staging-maven-plugin
and see how they do it.
And try to use this in the future.







On Sat, Jan 3, 2026 at 12:17 PM Gregor Zurowski <gr...@list.zurowski.org>
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 <cl...@gmail.com> 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 <cl...@gmail.com>
> 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 <
> gregor@list.zurowski.org>
> > > 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 <cl...@gmail.com>
> > >> 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 <cl...@gmail.com>
> > >> 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 <
> claus.ibsen@gmail.com>
> > >> 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

Re: Camel 4.17.0 Release

[Gregor Zurowski <gr...@list.zurowski.org>]

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 <cl...@gmail.com> 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 <cl...@gmail.com> 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 <gr...@list.zurowski.org>
> > 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 <cl...@gmail.com>
> >> 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 <cl...@gmail.com>
> >> 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 <cl...@gmail.com>
> >> 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

Re: Camel 4.17.0 Release

[Claus Ibsen <cl...@gmail.com>]

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 <cl...@gmail.com> 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 <gr...@list.zurowski.org>
> 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 <cl...@gmail.com>
>> 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 <cl...@gmail.com>
>> 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 <cl...@gmail.com>
>> 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

Re: Camel 4.17.0 Release

[Claus Ibsen <cl...@gmail.com>]

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 <gr...@list.zurowski.org>
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 <cl...@gmail.com> 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 <cl...@gmail.com>
> 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 <cl...@gmail.com>
> 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