Hi

+1

I have created a JIRA ticket about this
https://issues.apache.org/jira/browse/CAMEL-14715

Andrea I think you helped last time with setting up for both SB and examples.
We need a repo for this named: camel-karaf


On Fri, Mar 13, 2020 at 10:00 AM Andrea Cosentino
<ancosen1...@yahoo.com.invalid> wrote:
>
> Hello,
>
> We already moved the Spring Boot code and all the SB starters into a 
> separated git repository for convenience and to make the core independent. 
> And the same was done for Camel Quarkus, which started as a separated sub 
> project from the beginning. And we also recently moved the examples out into 
> its own git repository.
>
> We should do the same for Karaf/OSGi support for multiple reasons:
> - Having a separated repository will make easier and faster to release new 
> stuff and fixes without rebuilding the core part (this would be something 
> really useful)
> - We could have separated documentation as we already have for Spring Boot
> - We could make the main camel repository lighter
> - It’s much easier to find code related to OSGi/Karaf as its all together in
> - We can then add Karaf as a sub project to the Camel website (see projects 
> menu item)
> - We can have separated documentation on the website for Karaf/OSGi
> - We can generate a list of components that are supported in Karaf/OSGi and 
> also publish this on the website
>
> If we follow this path, we could be able to add new supported platforms in 
> the future without having to modify the core part.
>
> We envision that we only need to move core/camel-core-osgi, and all the osgi 
> components, and together with the karaf features and karaf commands, and the 
> itests. We will continue to generate OSGi MANIFEST.MF in the JARs from the 
> main Camel so they are still OSGi bundles.
>
> The end result would essentially be the same as today. Camel will continue to 
> be supported and work on Karaf.
>
> And we think we should do this before the first LTS release of Apache Camel, 
> which is planned to be Camel 3.3.0. So ideally we get this done for Camel 
> 3.2.0 so more people in the community can get their hands on a release and 
> provide feedback.
>
> This will require some effort but we do believe it’s worth the work.
>
> Thoughts?
>
> --
> Andrea Cosentino
> ----------------------------------
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: ancosen1...@yahoo.com
> Twitter: @oscerd2
> Github: oscerd



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Reply via email to