On 04/06/2024 11.17 am, Jean-Baptiste Onofré wrote:
Hi folks,
Hey JB,
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
Awesome. There seem to be a lot of upgrades which are missing in 4.4.6. Random picks from versions:display-dependency-updates show:
[INFO] commons-logging:commons-logging ....................... 1.3.1 -> 1.3.2 [INFO] org.apache.felix:org.apache.felix.cm.json ............. 1.0.6 -> 2.0.6 [INFO] org.apache.felix:org.apache.felix.configurator ...... 1.0.16 -> 1.0.18 [INFO] org.apache.felix:org.apache.felix.http.jetty ......... 4.2.2 -> 5.1.14 [INFO] org.apache.felix:org.apache.felix.inventory ........... 1.1.0 -> 2.0.0 [INFO] org.apache.felix:org.apache.felix.scr ................ 2.2.6 -> 2.2.10 [INFO] org.apache.felix:org.apache.felix.webconsole ......... 4.8.12 -> 5.0.2 [INFO] org.apache.felix:org.apache.felix.webconsole.plugins.ds ... [INFO] 2.2.0 -> 2.3.0 [INFO] org.apache.felix:org.apache.felix.webconsole.plugins.event ... [INFO] 1.1.8 -> 1.2.0 [INFO] org.apache.felix:org.apache.felix.webconsole.plugins.memoryusage ... [INFO] 1.0.10 -> 1.1.0 [INFO] org.eclipse.platform:org.eclipse.equinox.coordinator ... [INFO] 1.5.200 -> 1.5.300 [INFO] org.eclipse.platform:org.eclipse.equinox.region ... 1.5.300 -> 1.5.500 [INFO] org.eclipse.platform:org.eclipse.osgi ............... 3.18.0 -> 3.19.0 [INFO] org.jline:jline ..................................... 3.21.0 -> 3.26.1
There probably are a few others.
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
Cool.I am sorry for lack of contributions lately, but there's a ton of stuff requiring my attention downstream.
I would hope for karaf-4.5.0 to be strongly opined in terms of: - java-9+ way of doing things - pax-web-9, i.e. servlet-api-4 The former will allow a lot of special-case code to be removed.The latter is actually blocking downstreams from using things like Apache Shiro 2.0.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.
Neat.
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).
Now that you mention pax-exam, can anyone on this list spin a new release? There's a ton of updates which are not available in a release, like the 'pick a free port' changes, etc.
Also, OpenDaylight has a maven plugin to run pax-exam-based validation of a generated feature.xml (see https://github.com/opendaylight/odlparent/tree/master/features-test-plugin) -- would you be interested in having that in karaf.git?
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).
Sounds fine for others, but I must say we in OpenDaylight are quite invested in the convenience of dynamic services and their management as offered by Declarative Services (OSGi Compendium chapter 112) and its integration with Config Admin (chapter 104) and Metatype (chapter 105).
A sincere, uninformed question: is there anything out there which provides a comparable developer experience?
As I mentioned previously, we care about pax-web integration right now, but we expect to move away from it (and related OSGi standards) in very much immediate future (<18 months). I expect we will care about pax-jdbc integration for longer that, unless there is a compelling alternative.
Having said that, we are okay to integrate these ourselves, without reliance on Karaf providing them.
Regards, Robert
OpenPGP_signature.asc
Description: OpenPGP digital signature
