Re: Camel 3.22 issues with route ID

Hi You can also use nodePrefixId to help make unique ids easier, which you can set on routes On Tue, Apr 16, 2024 at 9:49 AM Claus Ibsen wrote: > Hi > > This is correct as-is. You should not have duplicate ids, its your problem > to fix that. > > On Tue, Apr 16, 2024 at 9:23 AM Michael

Re: Managing Quarkus dependencies when working with Native build

Could you be more specific, please? I can add line below, but that’s for runtime. I need to figure out design time - to prevent VS Code complaining about missing dependencies. // camel-k: dependency=mvn:org.apache.camel.quarkus:camel-quarkus-core Thanks, Vlad > On 15. 4. 2024, at 16:43,

Re: Camel 3.22 issues with route ID

Hi This is correct as-is. You should not have duplicate ids, its your problem to fix that. On Tue, Apr 16, 2024 at 9:23 AM Michael Rambichler wrote: > Hi, > > > > we recently switched from Camel 3.18 to Camel 3.22 and we discovered > following issue in some of our applications: > > > > We have

Camel 3.22 issues with route ID

Hi, we recently switched from Camel 3.18 to Camel 3.22 and we discovered following issue in some of our applications: We have several applications that use e.g. openapi generator to create separate route builder classes, a minimal reproducible example is: @Component public final class