Hello, I think there is some work to do to drop Java 17 in Camel Jbang part. In case, the risk of conflicts is high with planned changes on Camel Jbang cli, would it be possible to wait for Java 17 drop before starting on Camel Jbang CLI? I think Java 17 drop should be finished at worst mid of next week. (I feel not enough familiar with Camel Jbang internals and the planned overhaul to know if it will really bring a lot of conflicts so maybe that's not really a concern and both could go in parallel.)
And just in case synergy is possible, I think it is interesting to keep in mind, if there is a big overhaul that currently the camel jbang core tests are not parallelized and are taken almost 20% of the time almost alone when using the -T1C option on Jenkins CI. In case, while doing the work, there are possibilities to make it possible to have it in parallel at the same time that would be nice. If too complicated to think of both at same time, not a problem we can still get back to it later on. regards, ________________________________ From: Claus Ibsen <[email protected]> Sent: Thursday, October 15, 2026 5:41 PM To: dev <[email protected]> Subject: [EXTERNAL] Camel JBang CLI overhaul work for 4.24 Hi Part of the work for Camel 4.24 is to overhaul our codebase for camel-jbang CLI commands. So we are doing this now, so expect a set of PRs coming up that help improve, harden and fix this codebase over the coming days/week. -- 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
