You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by Jean-Baptiste Onofré <jb...@nanthrax.net> on 2025/02/21 07:40:58 UTC

[HEADS UP] Preparing Apache Karaf 4.5.0

Hi folks,

I would like to share the roadmap to Karaf 4.5.0.

Karaf 4.5.0 will contain:
- a new "simple" features service (flat/simple resolver)
- new Karaf core services as alternatives to Pax * modules (replacing
Pax Logging by karaf-logging, replace Pax URL by karaf-url (with just
the JDK HTTP Client), ...
- more Karaf distributions, opinionated about the content: minimal (as
today but without Pax * cooupliing), simple (with the simple features
service, the alternatives to Pax *, ..), standard (the same as today
but with updated versions, we will discuss to "promote" simple as
standard for Karaf 4.6.x), integration (based on standard with Camel,
ActiveMQ, ...), cloud (based on simple with opentelemetry, k8s
support, ..., by default)

As we did for Decanter, I will use Karaf 4.5.0 milestone to switch to GitHub:
- GitHub Issues instead of Jira (the idea is not to migrate everything
from Jira to GH Issues, but to do it "manually" to do a meaningful
triage.
- GitHub Actions instead of Jenkins for CI/CD
It works well for Decanter (https://github.com/apache/karaf-decanter).

Another work we should do is about the website. I think it would be
great to use Docusaurus to facilitate the updates and maintenance.
Website content should be updated too, including easily the
documentation on the website (thanks to md).
Any volunteers for that ?

So, now about the ETA:
1. Regarding "move to GitHub", if no objection, I will start the
effort today, creating .asf.yaml, GH workflows, creating GH Issues
with milestones
2. Regarding the new "simple" features service, I already have
something. I think I can have a PR by end of next week.
3. Regarding the new karaf services (alternatives to Pax *), I have
karaf-logging and karaf-url almost done (PRs will follow ~ 2 weeks). I
started karaf-web (powered by Tomcat, not depending on OSGi
HttpService, it's a pure Karaf Http service). I should be able to
share a draft PR.
Reasonably, we can plan Karaf 4.5.0 with all this in May.

However, I have a question for the community: maybe, considering the
number of important changes, it makes sense to use Karaf 5.0.0 instead
of 4.5.0 ? Thoughts ?

Thanks !
Regards
JB

Re: [HEADS UP] Preparing Apache Karaf 4.5.0

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi folks

I don't see any objection and a consensus on the roadmap.

Here's the next steps:
1. I will update the main branch with 5.0.0-SNAPSHOT version
2. I will enable github resources via .asf.yaml (issues, projects, discussions)
3. I will move from Jenkins to GH Actions
4. I will create GH issues and milestones populating the 5.0.0 roadmap
we discussed in this thread
5. I will start to create my PRs about new features service and karaf services

Regards
JB

On Fri, Feb 21, 2025 at 8:40 AM Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>
> Hi folks,
>
> I would like to share the roadmap to Karaf 4.5.0.
>
> Karaf 4.5.0 will contain:
> - a new "simple" features service (flat/simple resolver)
> - new Karaf core services as alternatives to Pax * modules (replacing
> Pax Logging by karaf-logging, replace Pax URL by karaf-url (with just
> the JDK HTTP Client), ...
> - more Karaf distributions, opinionated about the content: minimal (as
> today but without Pax * cooupliing), simple (with the simple features
> service, the alternatives to Pax *, ..), standard (the same as today
> but with updated versions, we will discuss to "promote" simple as
> standard for Karaf 4.6.x), integration (based on standard with Camel,
> ActiveMQ, ...), cloud (based on simple with opentelemetry, k8s
> support, ..., by default)
>
> As we did for Decanter, I will use Karaf 4.5.0 milestone to switch to GitHub:
> - GitHub Issues instead of Jira (the idea is not to migrate everything
> from Jira to GH Issues, but to do it "manually" to do a meaningful
> triage.
> - GitHub Actions instead of Jenkins for CI/CD
> It works well for Decanter (https://github.com/apache/karaf-decanter).
>
> Another work we should do is about the website. I think it would be
> great to use Docusaurus to facilitate the updates and maintenance.
> Website content should be updated too, including easily the
> documentation on the website (thanks to md).
> Any volunteers for that ?
>
> So, now about the ETA:
> 1. Regarding "move to GitHub", if no objection, I will start the
> effort today, creating .asf.yaml, GH workflows, creating GH Issues
> with milestones
> 2. Regarding the new "simple" features service, I already have
> something. I think I can have a PR by end of next week.
> 3. Regarding the new karaf services (alternatives to Pax *), I have
> karaf-logging and karaf-url almost done (PRs will follow ~ 2 weeks). I
> started karaf-web (powered by Tomcat, not depending on OSGi
> HttpService, it's a pure Karaf Http service). I should be able to
> share a draft PR.
> Reasonably, we can plan Karaf 4.5.0 with all this in May.
>
> However, I have a question for the community: maybe, considering the
> number of important changes, it makes sense to use Karaf 5.0.0 instead
> of 4.5.0 ? Thoughts ?
>
> Thanks !
> Regards
> JB

Re: [HEADS UP] Preparing Apache Karaf 4.5.0

Posted by Robert Varga <ni...@hq.sk.INVALID>.
On 21/02/2025 8.40 am, Jean-Baptiste Onofré wrote:
> However, I have a question for the community: maybe, considering the
> number of important changes, it makes sense to use Karaf 5.0.0 instead
> of 4.5.0 ? Thoughts ?

Hey JB, thanks for the great work.

Originally we wanted to do 4.5.0 with ... pax-web-9 and Java 11. 
Unfortunately I just don't seem to get enough cycles to do that 
maven.compiler.release=11 patch -- it runs contrary to the copied 
classes with which we are patching javax.xml and other packages :(

At any rate, given the sheer number of options now, yea, a karaf-5 may 
be appropriate.

Regards,
Robert

Re: [HEADS UP] Preparing Apache Karaf 4.5.0

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Mark

The idea is to have Karaf services specific to cloud features:
- Karaf service to populate configuration from k8s ConfigMap
- provided HELM charts base to easily deploy on k8s
- ...

The documentation will be completely reshape as part of 5.0.0
initiative (promoting/describing the distributions, etc).

Regards
JB

On Fri, Feb 21, 2025 at 10:44 AM Mark Derricutt <ma...@talios.com> wrote:
>
>  On 21 Feb 2025 at 8:40:58 PM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>
> > cloud (based on simple with opentelemetry, k8s
> > support, ..., by default)
> >
>
> Is there any details/documentation on this cloud flavour anywhere at all?
>
> Mak
>
>
> --
> "Great artists are extremely selfish and arrogant things" — Steven Wilson,
> Porcupine Tree

Re: [HEADS UP] Preparing Apache Karaf 4.5.0

Posted by Mark Derricutt <ma...@talios.com>.
 On 21 Feb 2025 at 8:40:58 PM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:

> cloud (based on simple with opentelemetry, k8s
> support, ..., by default)
>

Is there any details/documentation on this cloud flavour anywhere at all?

Mak


-- 
"Great artists are extremely selfish and arrogant things" — Steven Wilson,
Porcupine Tree

Re: [HEADS UP] Preparing Apache Karaf 4.5.0

Posted by Matt Pavlovich <ma...@gmail.com>.
+1   having pax-web v10 support in Karaf 4.5/5 will also allow users to be able to have a stable fallback while the new Karaf services are coming online and reaching feature parity.

Thanks!

> On Feb 26, 2025, at 7:27 AM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> 
> Hi Grzegorz
> 
> There's no problem about using GH Issues on ASF projects: several
> projects are already using that.
> Also, the ASF Infra is supporting GitHub Actions (for security
> reasons, they are managing the allowed GH Actions
> https://infra.apache.org/github-actions-policy.html).
> 
> Yes, as discussed, I think we should avoid any inner <repository/> in
> our features repositories. It's way more flexible and allow users to
> easily update/manage dependencies.
> I'm working on a new PRs about that.
> 
> For Pax Web 10, you do an amazing job, thanks again for that !
> I reinforced what I said in my previous email: Pax *, including Pax
> Web, will still be supported and packaged in Karaf. We "just" create a
> new distribution with Karaf "core" services.
> 
> Thanks !
> Regards
> JB
> 
> On Wed, Feb 26, 2025 at 7:39 AM Grzegorz Grzybek <gr...@gmail.com> wrote:
>> 
>> Hello
>> 
>> My 2¢ about Pax. I don't have any strong opinion on the plan and I simply
>> agree. I was only wondering about ASF governance - is it ok to move
>> (fully/partially/automatically/manually) from issues.apache.org to GH?
>> 
>> Now about Pax - as suggested, I see <repository> for pax web is almost
>> removed from Karaf standard features (
>> https://github.com/apache/karaf/pull/1934). This makes Karaf distro ready
>> to install any features you like regarding web without strong opinion on
>> which (pax? felix-http?) is "opinionated" by Karaf.
>> 
>> Pax Web 8 (Jetty 9, Tomcat 9, Undertow 2.2, JDK8+) and 9 (Jetty 10, Tomcat
>> 9, Undertow 2.2, JDK11+) are in kind of maintenance mode - I fix issues
>> (thanks community!) as they arrive and I try to keep runtimes up to date.
>> 
>> Last week I've rebased my work on Pax Web 10 (Jetty 12, Tomcat 10.1,
>> Undertow 2.3, JDK 17+) on top of latest Pax Web 9 and as discussed almost
>> all I need is ready:
>> 
>>   - OSGi CMPN 8.1 no longer includes "chapter 102: HttpService", so I
>>   moved this interface to org.ops4j.pax.web.service package - there's no
>>   other option
>>   - OSGi CMPN 8.1 chapter 140 (Servlet Whiteboard) is implemented in Pax
>>   Web 10 - I used it to check if Jolokia 2 (jakarta.servlet based) can be
>>   whiteboard-registered
>>   - OSGi CMPN 8.1 chapter 128 (Web Applications) is not updated from
>>   javax.servlet to jakarta.servlet, but this kind of "special" OSGi CMPN
>>   specification, because there's no API, only definition of some behaviors
>>   related to deployment of WARs - and most of the work (OSGi-fying non-OSGi
>>   WAR archives) is done by Pax URL 3.0 (not released yet, see
>>   https://github.com/ops4j/org.ops4j.pax.url/commits/url-3.0.x/)
>> 
>> What held me in November 2023 (when I stopped working on Pax Web 10) was
>> not the difficulty of OSGi CMPN implementation (it was roughly done), but
>> the amount of itests in Pax Web 8/9 that didn't work in Pax Web 10 - but
>> mostly related to things like CDI, JSF and Aries JAX-RS (based on CXF).
>> The problem was the quality of jakarta.servlet based libraries which were
>> not proper OSGi bundles (MyFaces, Prime Faces, Weld, Aries, ...)
>> 
>> So now after I spent some time rebasing, I want to release Pax Web 10 soon™
>> without bothering too much on _all_ MyFaces/PrimeFaces/CDI tests. I'll keep
>> you informed.
>> 
>> kind regards
>> Grzegorz Grzybek
>> 
>> pt., 21 lut 2025 o 08:41 Jean-Baptiste Onofré <jb...@nanthrax.net> napisał(a):
>> 
>>> Hi folks,
>>> 
>>> I would like to share the roadmap to Karaf 4.5.0.
>>> 
>>> Karaf 4.5.0 will contain:
>>> - a new "simple" features service (flat/simple resolver)
>>> - new Karaf core services as alternatives to Pax * modules (replacing
>>> Pax Logging by karaf-logging, replace Pax URL by karaf-url (with just
>>> the JDK HTTP Client), ...
>>> - more Karaf distributions, opinionated about the content: minimal (as
>>> today but without Pax * cooupliing), simple (with the simple features
>>> service, the alternatives to Pax *, ..), standard (the same as today
>>> but with updated versions, we will discuss to "promote" simple as
>>> standard for Karaf 4.6.x), integration (based on standard with Camel,
>>> ActiveMQ, ...), cloud (based on simple with opentelemetry, k8s
>>> support, ..., by default)
>>> 
>>> As we did for Decanter, I will use Karaf 4.5.0 milestone to switch to
>>> GitHub:
>>> - GitHub Issues instead of Jira (the idea is not to migrate everything
>>> from Jira to GH Issues, but to do it "manually" to do a meaningful
>>> triage.
>>> - GitHub Actions instead of Jenkins for CI/CD
>>> It works well for Decanter (https://github.com/apache/karaf-decanter).
>>> 
>>> Another work we should do is about the website. I think it would be
>>> great to use Docusaurus to facilitate the updates and maintenance.
>>> Website content should be updated too, including easily the
>>> documentation on the website (thanks to md).
>>> Any volunteers for that ?
>>> 
>>> So, now about the ETA:
>>> 1. Regarding "move to GitHub", if no objection, I will start the
>>> effort today, creating .asf.yaml, GH workflows, creating GH Issues
>>> with milestones
>>> 2. Regarding the new "simple" features service, I already have
>>> something. I think I can have a PR by end of next week.
>>> 3. Regarding the new karaf services (alternatives to Pax *), I have
>>> karaf-logging and karaf-url almost done (PRs will follow ~ 2 weeks). I
>>> started karaf-web (powered by Tomcat, not depending on OSGi
>>> HttpService, it's a pure Karaf Http service). I should be able to
>>> share a draft PR.
>>> Reasonably, we can plan Karaf 4.5.0 with all this in May.
>>> 
>>> However, I have a question for the community: maybe, considering the
>>> number of important changes, it makes sense to use Karaf 5.0.0 instead
>>> of 4.5.0 ? Thoughts ?
>>> 
>>> Thanks !
>>> Regards
>>> JB
>>> 


Re: [HEADS UP] Preparing Apache Karaf 4.5.0

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Grzegorz

There's no problem about using GH Issues on ASF projects: several
projects are already using that.
Also, the ASF Infra is supporting GitHub Actions (for security
reasons, they are managing the allowed GH Actions
https://infra.apache.org/github-actions-policy.html).

Yes, as discussed, I think we should avoid any inner <repository/> in
our features repositories. It's way more flexible and allow users to
easily update/manage dependencies.
I'm working on a new PRs about that.

For Pax Web 10, you do an amazing job, thanks again for that !
I reinforced what I said in my previous email: Pax *, including Pax
Web, will still be supported and packaged in Karaf. We "just" create a
new distribution with Karaf "core" services.

Thanks !
Regards
JB

On Wed, Feb 26, 2025 at 7:39 AM Grzegorz Grzybek <gr...@gmail.com> wrote:
>
> Hello
>
> My 2¢ about Pax. I don't have any strong opinion on the plan and I simply
> agree. I was only wondering about ASF governance - is it ok to move
> (fully/partially/automatically/manually) from issues.apache.org to GH?
>
> Now about Pax - as suggested, I see <repository> for pax web is almost
> removed from Karaf standard features (
> https://github.com/apache/karaf/pull/1934). This makes Karaf distro ready
> to install any features you like regarding web without strong opinion on
> which (pax? felix-http?) is "opinionated" by Karaf.
>
> Pax Web 8 (Jetty 9, Tomcat 9, Undertow 2.2, JDK8+) and 9 (Jetty 10, Tomcat
> 9, Undertow 2.2, JDK11+) are in kind of maintenance mode - I fix issues
> (thanks community!) as they arrive and I try to keep runtimes up to date.
>
> Last week I've rebased my work on Pax Web 10 (Jetty 12, Tomcat 10.1,
> Undertow 2.3, JDK 17+) on top of latest Pax Web 9 and as discussed almost
> all I need is ready:
>
>    - OSGi CMPN 8.1 no longer includes "chapter 102: HttpService", so I
>    moved this interface to org.ops4j.pax.web.service package - there's no
>    other option
>    - OSGi CMPN 8.1 chapter 140 (Servlet Whiteboard) is implemented in Pax
>    Web 10 - I used it to check if Jolokia 2 (jakarta.servlet based) can be
>    whiteboard-registered
>    - OSGi CMPN 8.1 chapter 128 (Web Applications) is not updated from
>    javax.servlet to jakarta.servlet, but this kind of "special" OSGi CMPN
>    specification, because there's no API, only definition of some behaviors
>    related to deployment of WARs - and most of the work (OSGi-fying non-OSGi
>    WAR archives) is done by Pax URL 3.0 (not released yet, see
>    https://github.com/ops4j/org.ops4j.pax.url/commits/url-3.0.x/)
>
> What held me in November 2023 (when I stopped working on Pax Web 10) was
> not the difficulty of OSGi CMPN implementation (it was roughly done), but
> the amount of itests in Pax Web 8/9 that didn't work in Pax Web 10 - but
> mostly related to things like CDI, JSF and Aries JAX-RS (based on CXF).
> The problem was the quality of jakarta.servlet based libraries which were
> not proper OSGi bundles (MyFaces, Prime Faces, Weld, Aries, ...)
>
> So now after I spent some time rebasing, I want to release Pax Web 10 soon™
> without bothering too much on _all_ MyFaces/PrimeFaces/CDI tests. I'll keep
> you informed.
>
> kind regards
> Grzegorz Grzybek
>
> pt., 21 lut 2025 o 08:41 Jean-Baptiste Onofré <jb...@nanthrax.net> napisał(a):
>
> > Hi folks,
> >
> > I would like to share the roadmap to Karaf 4.5.0.
> >
> > Karaf 4.5.0 will contain:
> > - a new "simple" features service (flat/simple resolver)
> > - new Karaf core services as alternatives to Pax * modules (replacing
> > Pax Logging by karaf-logging, replace Pax URL by karaf-url (with just
> > the JDK HTTP Client), ...
> > - more Karaf distributions, opinionated about the content: minimal (as
> > today but without Pax * cooupliing), simple (with the simple features
> > service, the alternatives to Pax *, ..), standard (the same as today
> > but with updated versions, we will discuss to "promote" simple as
> > standard for Karaf 4.6.x), integration (based on standard with Camel,
> > ActiveMQ, ...), cloud (based on simple with opentelemetry, k8s
> > support, ..., by default)
> >
> > As we did for Decanter, I will use Karaf 4.5.0 milestone to switch to
> > GitHub:
> > - GitHub Issues instead of Jira (the idea is not to migrate everything
> > from Jira to GH Issues, but to do it "manually" to do a meaningful
> > triage.
> > - GitHub Actions instead of Jenkins for CI/CD
> > It works well for Decanter (https://github.com/apache/karaf-decanter).
> >
> > Another work we should do is about the website. I think it would be
> > great to use Docusaurus to facilitate the updates and maintenance.
> > Website content should be updated too, including easily the
> > documentation on the website (thanks to md).
> > Any volunteers for that ?
> >
> > So, now about the ETA:
> > 1. Regarding "move to GitHub", if no objection, I will start the
> > effort today, creating .asf.yaml, GH workflows, creating GH Issues
> > with milestones
> > 2. Regarding the new "simple" features service, I already have
> > something. I think I can have a PR by end of next week.
> > 3. Regarding the new karaf services (alternatives to Pax *), I have
> > karaf-logging and karaf-url almost done (PRs will follow ~ 2 weeks). I
> > started karaf-web (powered by Tomcat, not depending on OSGi
> > HttpService, it's a pure Karaf Http service). I should be able to
> > share a draft PR.
> > Reasonably, we can plan Karaf 4.5.0 with all this in May.
> >
> > However, I have a question for the community: maybe, considering the
> > number of important changes, it makes sense to use Karaf 5.0.0 instead
> > of 4.5.0 ? Thoughts ?
> >
> > Thanks !
> > Regards
> > JB
> >

Re: [HEADS UP] Preparing Apache Karaf 4.5.0

Posted by Grzegorz Grzybek <gr...@gmail.com>.
Hello

My 2¢ about Pax. I don't have any strong opinion on the plan and I simply
agree. I was only wondering about ASF governance - is it ok to move
(fully/partially/automatically/manually) from issues.apache.org to GH?

Now about Pax - as suggested, I see <repository> for pax web is almost
removed from Karaf standard features (
https://github.com/apache/karaf/pull/1934). This makes Karaf distro ready
to install any features you like regarding web without strong opinion on
which (pax? felix-http?) is "opinionated" by Karaf.

Pax Web 8 (Jetty 9, Tomcat 9, Undertow 2.2, JDK8+) and 9 (Jetty 10, Tomcat
9, Undertow 2.2, JDK11+) are in kind of maintenance mode - I fix issues
(thanks community!) as they arrive and I try to keep runtimes up to date.

Last week I've rebased my work on Pax Web 10 (Jetty 12, Tomcat 10.1,
Undertow 2.3, JDK 17+) on top of latest Pax Web 9 and as discussed almost
all I need is ready:

   - OSGi CMPN 8.1 no longer includes "chapter 102: HttpService", so I
   moved this interface to org.ops4j.pax.web.service package - there's no
   other option
   - OSGi CMPN 8.1 chapter 140 (Servlet Whiteboard) is implemented in Pax
   Web 10 - I used it to check if Jolokia 2 (jakarta.servlet based) can be
   whiteboard-registered
   - OSGi CMPN 8.1 chapter 128 (Web Applications) is not updated from
   javax.servlet to jakarta.servlet, but this kind of "special" OSGi CMPN
   specification, because there's no API, only definition of some behaviors
   related to deployment of WARs - and most of the work (OSGi-fying non-OSGi
   WAR archives) is done by Pax URL 3.0 (not released yet, see
   https://github.com/ops4j/org.ops4j.pax.url/commits/url-3.0.x/)

What held me in November 2023 (when I stopped working on Pax Web 10) was
not the difficulty of OSGi CMPN implementation (it was roughly done), but
the amount of itests in Pax Web 8/9 that didn't work in Pax Web 10 - but
mostly related to things like CDI, JSF and Aries JAX-RS (based on CXF).
The problem was the quality of jakarta.servlet based libraries which were
not proper OSGi bundles (MyFaces, Prime Faces, Weld, Aries, ...)

So now after I spent some time rebasing, I want to release Pax Web 10 soon™
without bothering too much on _all_ MyFaces/PrimeFaces/CDI tests. I'll keep
you informed.

kind regards
Grzegorz Grzybek

pt., 21 lut 2025 o 08:41 Jean-Baptiste Onofré <jb...@nanthrax.net> napisał(a):

> Hi folks,
>
> I would like to share the roadmap to Karaf 4.5.0.
>
> Karaf 4.5.0 will contain:
> - a new "simple" features service (flat/simple resolver)
> - new Karaf core services as alternatives to Pax * modules (replacing
> Pax Logging by karaf-logging, replace Pax URL by karaf-url (with just
> the JDK HTTP Client), ...
> - more Karaf distributions, opinionated about the content: minimal (as
> today but without Pax * cooupliing), simple (with the simple features
> service, the alternatives to Pax *, ..), standard (the same as today
> but with updated versions, we will discuss to "promote" simple as
> standard for Karaf 4.6.x), integration (based on standard with Camel,
> ActiveMQ, ...), cloud (based on simple with opentelemetry, k8s
> support, ..., by default)
>
> As we did for Decanter, I will use Karaf 4.5.0 milestone to switch to
> GitHub:
> - GitHub Issues instead of Jira (the idea is not to migrate everything
> from Jira to GH Issues, but to do it "manually" to do a meaningful
> triage.
> - GitHub Actions instead of Jenkins for CI/CD
> It works well for Decanter (https://github.com/apache/karaf-decanter).
>
> Another work we should do is about the website. I think it would be
> great to use Docusaurus to facilitate the updates and maintenance.
> Website content should be updated too, including easily the
> documentation on the website (thanks to md).
> Any volunteers for that ?
>
> So, now about the ETA:
> 1. Regarding "move to GitHub", if no objection, I will start the
> effort today, creating .asf.yaml, GH workflows, creating GH Issues
> with milestones
> 2. Regarding the new "simple" features service, I already have
> something. I think I can have a PR by end of next week.
> 3. Regarding the new karaf services (alternatives to Pax *), I have
> karaf-logging and karaf-url almost done (PRs will follow ~ 2 weeks). I
> started karaf-web (powered by Tomcat, not depending on OSGi
> HttpService, it's a pure Karaf Http service). I should be able to
> share a draft PR.
> Reasonably, we can plan Karaf 4.5.0 with all this in May.
>
> However, I have a question for the community: maybe, considering the
> number of important changes, it makes sense to use Karaf 5.0.0 instead
> of 4.5.0 ? Thoughts ?
>
> Thanks !
> Regards
> JB
>

Re: [HEADS UP] Preparing Apache Karaf 4.5.0

Posted by Francois Papon <fr...@openobject.fr>.
Hi JB,

I'm fully agree with all these points!

About the versioning, as we want to do a lot of major changes, I think
it would be better to move on 5.0.0 instead of 4.5.0.

I also like the move to full GitHub, it would help a lot the community.

regards,

François
fpapon@apache.org
francois.papon@openobject.fr

Le 21/02/2025 à 08:40, Jean-Baptiste Onofré a écrit :
> Hi folks,
>
> I would like to share the roadmap to Karaf 4.5.0.
>
> Karaf 4.5.0 will contain:
> - a new "simple" features service (flat/simple resolver)
> - new Karaf core services as alternatives to Pax * modules (replacing
> Pax Logging by karaf-logging, replace Pax URL by karaf-url (with just
> the JDK HTTP Client), ...
> - more Karaf distributions, opinionated about the content: minimal (as
> today but without Pax * cooupliing), simple (with the simple features
> service, the alternatives to Pax *, ..), standard (the same as today
> but with updated versions, we will discuss to "promote" simple as
> standard for Karaf 4.6.x), integration (based on standard with Camel,
> ActiveMQ, ...), cloud (based on simple with opentelemetry, k8s
> support, ..., by default)
>
> As we did for Decanter, I will use Karaf 4.5.0 milestone to switch to GitHub:
> - GitHub Issues instead of Jira (the idea is not to migrate everything
> from Jira to GH Issues, but to do it "manually" to do a meaningful
> triage.
> - GitHub Actions instead of Jenkins for CI/CD
> It works well for Decanter (https://github.com/apache/karaf-decanter).
>
> Another work we should do is about the website. I think it would be
> great to use Docusaurus to facilitate the updates and maintenance.
> Website content should be updated too, including easily the
> documentation on the website (thanks to md).
> Any volunteers for that ?
>
> So, now about the ETA:
> 1. Regarding "move to GitHub", if no objection, I will start the
> effort today, creating .asf.yaml, GH workflows, creating GH Issues
> with milestones
> 2. Regarding the new "simple" features service, I already have
> something. I think I can have a PR by end of next week.
> 3. Regarding the new karaf services (alternatives to Pax *), I have
> karaf-logging and karaf-url almost done (PRs will follow ~ 2 weeks). I
> started karaf-web (powered by Tomcat, not depending on OSGi
> HttpService, it's a pure Karaf Http service). I should be able to
> share a draft PR.
> Reasonably, we can plan Karaf 4.5.0 with all this in May.
>
> However, I have a question for the community: maybe, considering the
> number of important changes, it makes sense to use Karaf 5.0.0 instead
> of 4.5.0 ? Thoughts ?
>
> Thanks !
> Regards
> JB