1. Sounds good
2. I think Jetty 12 / pax-web support in v4.5.x is important. I started working
on a PR for it, but there are significant Jetty API changes. (Jetty 12 support
would provide a LTS-like support timeframe while Karaf 5.x gets going.)
3. +1 on JUnit 5 Extension / Runner instead of pax-exam
+1 on simplified default logger — One thing pax-logging’s wrapping provides
reload of config. Is the thought here to drop runtime reload of logging
configuration change?.
Regarding replacing pax-web — this seems like a large effort. There are a
*ton* of unit tests of various use cases there and lots of value covering a ton
of web-deployment scenarios. Are you thinking of dropping http whiteboard or
other deploy scenarios in favor of servlet-only? If the other scenarios are
required, perhaps keep pax-web and only go wtih Jetty/Tomcat support? I don’t
see a lot of demand / usage of Undertow.
4. Configuration and Encryption service (and encryption of config keys and
values) as first-class services instead of jasypt add-on. (JDK crypto
out-of-the-box).
My $0.02.
Thanks,
Matt Pavlovich
> On Jun 4, 2024, at 4:17 AM, Jean-Baptiste Onofré <[email protected]> wrote:
>
> Hi folks,
>
> I think it's time to prepare a new milestone for the project :)
>
> Short term (and first step) is to prepare the coming release:
>
> 1. Apache Karaf 4.4.7 will be submitted to vote next week. It will include:
> * Improvement on the spring features repository (providing both
> Spring 5 and Spring 6 features)
> * Dependencies updates and minor fixes found on the 4.4.6 release
>
> 2. Apache Karaf 4.5.0 will be submitted to vote by the end of the
> month. It will include (mainly):
> * New spec features repository with Jakarta specs
> * Bigger fixes for 4.5.0
>
> 3. Apache Karaf 5.0.0
> That's the big milestone, and I propose to have big and opinionated
> changes here. OSGi is an implementation detail of the runtime, still
> exposed to the experimented users.
> Be opinionated means that I propose to remove PAX * dependencies,
> and provide Karaf services instead, very simple and opinionated (for
> instance, instead of PAX Web, a simple Tomcat based service, instead
> of PAX Logging, a simple slf4j/log4j only service, Pax Exam replaced
> by JUnit 5 simple extensions, etc).
> Another goal of Karaf 5 is to bring new tooling to improve dev
> experience (annotation based distributions generation, etc).
> Also, users will be able to smoothly deploy Spring powered or
> Servlet applications without knowing/leveraging OSGi (especially the
> import/export pattern).
>
> Thoughts ?
>
> Regards
> JB
