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 <[email protected]> wrote: > Hi, > > I am having issues building the Spring Boot project. Initially, there > were issues with the maven-release-plugin, which I resolved by > removing the overridden dependency on maven-scm-provider-gitexe. Next, > the release:prepare phase created two staging repositories. I tried it > twice with the same result. Then I reverted the maven-release-plugin > upgrade (back to version 2.4.0), but now the release process creates > five staging repositories on every attempt. > > Any ideas on how to resolve this? > > Thanks, > Gregor > > On Sat, Jan 3, 2026 at 9:13 AM Claus Ibsen <[email protected]> wrote: > > > > Hi Gregor > > > > You may need to cherry pick this commit on camel-spring-boot for the > 4.17.0 > > release branch > > > https://github.com/apache/camel-spring-boot/commit/3fa9afb02176f778c6c5d1d33107cd1f6f5ddb86 > > > > Though you would likely see that when building 4.17.0 then you have > changed > > source files that this commit included. > > > > On Thu, Jan 1, 2026 at 5:01 PM Claus Ibsen <[email protected]> > wrote: > > > > > Hi Gregor > > > > > > Happy new year. > > > Yes you are welcome to start the 4.17.0 release. > > > > > > I have fixed RAT this morning and the code base should be okay. > > > > > > > > > > > > On Thu, Jan 1, 2026 at 3:44 PM Gregor Zurowski < > [email protected]> > > > wrote: > > > > > >> Happy New Year, everyone! > > >> > > >> I started to work on the 4.17.0 release. > > >> > > >> On Sat, Dec 27, 2025 at 8:59 AM Claus Ibsen <[email protected]> > > >> wrote: > > >> > > > >> > Hi > > >> > > > >> > I got word from Gregor. We can do 4.17.0 start of 2026 and that is > also > > >> > very good. > > >> > > > >> > > > >> > On Tue, Dec 23, 2025 at 9:04 AM Claus Ibsen <[email protected]> > > >> wrote: > > >> > > > >> > > Hi Gregor > > >> > > > > >> > > We can do the 4.17.0 release any time, if you for example want to > do > > >> it > > >> > > during this Christmas break. > > >> > > Just let us know and we plan accordingly. > > >> > > > > >> > > > > >> > > > > >> > > On Sun, Dec 7, 2025 at 10:00 AM Claus Ibsen < > [email protected]> > > >> wrote: > > >> > > > > >> > >> Hi > > >> > >> > > >> > >> It would be good to get a new release after the patch release, > or in > > >> the > > >> > >> first weeks of January. The 4.18 LTS is planned for February, > when > > >> 4.10 LTS > > >> > >> expires. > > >> > >> > > >> > >> But at first its more important to get the LTS patches released > > >> first. > > >> > >> > > >> > >> > > >> > >> > > >> > >> -- > > >> > >> Claus Ibsen > > >> > >> > > >> > > > > >> > > > > >> > > -- > > >> > > Claus Ibsen > > >> > > > > >> > > > >> > > > >> > -- > > >> > Claus Ibsen > > >> > > > > > > > > > -- > > > Claus Ibsen > > > > > > > > > -- > > Claus Ibsen > -- Claus Ibsen
