Hi Cameleers, I think this brings about another topic, that I talked about with Andrea briefly on Gitter, how do we manage the drift between camel-spring-boot and the changes made in Camel (main repository). What we came up with was to trigger the build of Camel Spring Boot after the build of Camel.
Since the majority of Spring Boot code is auto generated and committed to the git repository, the code generated at build could differ from the code in the git repository. For this we thought of attaching a patch as one of the build artefacts from building Camel Spring Boot. Then one of the committers would need to take that patch and apply/commit it to camel-spring-boot. Does that make sense? As an alternative, we could consider not committing the generated code and have it generated/packaged only at build time. zoran On Sat, Feb 8, 2020 at 5:14 PM Andrea Cosentino <anco...@gmail.com> wrote: > > The best way is always build camel actually and always run a build of > camel-,spring-boot > > Il sab 8 feb 2020, 17:12 Pascal Schumacher <pascalschumac...@gmx.net> ha > scritto: > > > Hi, > > > > after the Camel Spring Boot artifacts where moved into a separate > > repository it looks like snapshot artifacts are no longer published to > > the Apache Foundation Maven repository. > > > > What do you think about restoring the publication? > > > > Thanks, > > > > Pascal > > > > -- Zoran Regvart
