[HEADS UP] Apache Karaf runtime 4.4.7, 4.5.0, and beyond
Hi guys, I'm working on the next round of releases and roadmap. First, I will submit 4.4.7 to vote soon (I'm fixing the last tickets). This is a maintenance release, fixing several issues and upgrading dependencies. Then, I will focus on the 4.5.0 release with major changes: - a new feature service (simple) using a flat resolver. It will be an alternative to the regular feature service we have today. I will provide a PR and proposal in a separate email soon. - start to provide alternatives to Pax * projects. Karaf 4.5.x will still use Pax * by default, but we will have features for karaf/services alternatives I'm also working on a Karaf 5.x proposal, disruptive with Karaf 4.x. The purpose is to focus on key features for our users, with a much modern architecture. I will provide more details one 4.4.7 and 4.5.0 will be available. Stay tuned! Regards JB
Re: Using k8s secrets in Karaf
Hi, I think the interpolation syntax is different in Karaf (comparing to pure Felix). Let me check. Regards JB On Wed, Oct 30, 2024 at 7:33 AM Mark Derricutt wrote: > > Hey all, > > Have a question regarding support K8S secrets, in my Karaf > distribution/container image, I've patched the config.properties file and > updated the org.apache.felix.configadmin.plugin.interpolation.secretsdir entry > to a directory I'm mounting my secrets into. > > When using $[foo] in one of my .cfg files, I see the non-interpolated value > being passed to my component rather than what I'd expect. > > Am I likely missing something obvious, or do I need to include a specific > bundle for secrets? > > Mark > > -- > "Great artists are extremely selfish and arrogant things" — Steven Wilson, > Porcupine Tree
Re: Incorrect OSGI-INF/permissions.perm in org.apache.felix.configadmin-1.9.26.jar
Hi Chaz,
Thanks for the report, I will take a look and let you know.
About osgi-security, I think there's already a JDK21+ bundle
available. I have to check as well.
Regards
JB
On Wed, Sep 18, 2024 at 9:16 PM wrote:
>
> Hello,
>
> The permissions.perm file packaged with felix configadmin 1.9.26 and tested
> on latest Karaf is missing RuntimePermission/PropertyPermission
>
> java.security.AccessControlException: access denied
> ("java.lang.RuntimePermission"
> "getenv.ORG_APACHE_FELIX_FILEINSTALL_DEPLOY_FELIX_FILEINSTALL_ACTIVE_LEVEL")
> java.security.AccessControlException: access denied
> ("java.lang.RuntimePermission"
> "getenv.ORG_OPS4J_PAX_URL_MVN_FELIX_FILEINSTALL_FILENAME")
> java.security.AccessControlException: access denied
> ("java.lang.RuntimePermission" "getenv.ORG_OPS4J_PAX_LOGGING_COLOR_DEBUG")
>
> There are similar for those 3 with PropertyPermission.
>
> The following changes to permissions.perm fixes the issue:
>
> # Environment/Property Support
> (java.lang.RuntimePermission "*" "getenv.*")
> (java.util.PropertyPermission "*" "read")
>
> This is one of, if not the only, bundle in Karaf distrib i've seen with a
> permissions.perm file.
>
> You can confirm this issue by enabling osgi security and installing
> framework-security on felix or running equinox (enabled by default).
>
> A more general question:
>
> Is there a plan for osgi-security past JDK17? I'm planning to use it to
> verify JARs are signed from the proper groups before hot-deploying.
>
> --
> Chaz
Re: Board report for September 2024
Report has been sent. Thanks ! Regards JB On Wed, Sep 4, 2024 at 1:27 PM Grzegorz Grzybek wrote: > > Looks good, +1 > > thanks! > regards > Grzegorz Grzybek > > śr., 4 wrz 2024 o 13:23 Francois Papon > napisał(a): > > > Looks good to me! > > > > Thanks JB! > > > > regards, > > > > François > > > > On 04/09/2024 10:52, Jean-Baptiste Onofré wrote: > > > Hi folks, > > > > > > I prepared the board report for this month: > > > https://cwiki.apache.org/confluence/display/KARAF/Board+Reports > > > > > > Can you please take a look ? > > > > > > I would like to submit the report asap. > > > > > > Thanks ! > > > Regards > > > JB > >
Board report for September 2024
Hi folks, I prepared the board report for this month: https://cwiki.apache.org/confluence/display/KARAF/Board+Reports Can you please take a look ? I would like to submit the report asap. Thanks ! Regards JB
Re: [HEADS UP] Apache Karaf 4.4.7 release
Hi guys, I'm very sorry for being quiet recently (I have been on vacation and hooked by other tasks). I'm now back on Apache Karaf ! I'm resuming the 4.4.7 preparation (and also heading to 4.5.0). Regards JB On Mon, Jul 1, 2024 at 7:30 AM Jean-Baptiste Onofré wrote: > > Hi folks, > > As discussed previously, I'm preparing the Apache Karaf 4.4.7 release. > I have some fixes to merge: the vote should start mid this week. > > I will keep you posted. > > Thanks, > Regards > JB
Re: [HEADS UP] Apache Karaf 4.4.7 release
Hi Yes, it's planned: I'm working on SMX bundles preparation and I will update for Karaf 4.4.7. Working on it, I will keep you posted. Regards JB On Tue, Jul 9, 2024 at 5:56 PM Matt Pavlovich wrote: > > Hey JB- > > The Spring dependencies are a couple revs back. I just pushed up a couple PRs > to rev the Spring ServiceMix Bundles to be current for 5.3.x and 6.1.x. > > How do you feel about doing a ServiceMix Bundles release ahead of Karaf 4.4.7? > > Thanks, > Matt > > > On Jul 1, 2024, at 12:30 AM, Jean-Baptiste Onofré wrote: > > > > Hi folks, > > > > As discussed previously, I'm preparing the Apache Karaf 4.4.7 release. > > I have some fixes to merge: the vote should start mid this week. > > > > I will keep you posted. > > > > Thanks, > > Regards > > JB >
[HEADS UP] Apache Karaf 4.4.7 release
Hi folks, As discussed previously, I'm preparing the Apache Karaf 4.4.7 release. I have some fixes to merge: the vote should start mid this week. I will keep you posted. Thanks, Regards JB
Re: [PROPOSAL] Apache Karaf runtime releases and roadmap
That's true, and that's why it's opinionated :) The purpose is really to match 90% of the use cases. I think some features are interesting but require a lot of effort/maintenance for only a limited use. Regards JB On Thu, Jun 20, 2024 at 9:47 AM Grzegorz Grzybek wrote: > > Thanks for clarification JB! > > Just one more comment about: > > Tomcat for the Karaf Web service yes (not strong opinion here, it > > would be Jetty). And as state earlier, only Servlet/Filter service > > registration package will be supported. > > > That's quite arbitrary distinction TBH :) You know - we rarely write > servlets these days and rather have some kind of dispatcher servlet (yes, > this is spring...) which delegates to different views/controllers/handlers > etc. > However the point is that even if you DO write servlets, then: > >- servlets have access to ServletContext >- ServletContext gives you access to context attributes >- context attributes are either taken from web.xml () or >are setup in ServletContextListeners >- ServletContextListeners are 3rd "big thing" (next to servlets and >filters) that constitute web applications >- so you have to allow them too >- but ServletContextListeners allow you to dynamically register >additional servlets (that's what most SCIs do too - JSF, JSP, ...) >dynamically with dynamic mapping >- also servlets and filters may be protected - in web.xml you can have > and elements... > > I could continue (I've already mentioned JSPs, SCIs, ...) getting closer > and closer to full Servlet API specification... > > The point is that if you want servlets + filters only, you'd need full > implementation based on particular runtime (whether Tomcat, Jetty or > Undertow) to deal with its specifics (like Jetty's ServletContextHandler, > Tomcat's StandardContext or Undertow's DeploymentInfo). You also have to > deal with contexts (implementations of jakarta.servlet.ServletContext > interface) to separate servlets. Though Felix-Http has one "dispatcher > servlet" registered in single context and moves "context" concept from the > runtime to this servlet... > > Anyway - a lot of work ;) > > regards > Grzegorz Grzybek > > czw., 20 cze 2024 o 08:51 Jean-Baptiste Onofré napisał(a): > > > Hi Grzegorz > > > > Thanks for your message, it's highly appreciated. > > > > See my comments inline: > > > > > 1. What exactly are "Karaf services"? Are these OSGi services? > > (registered > > > with BundleContext.registerService(iface, object, properties)?) If not > > then > > > what are the aspects that make them "services" - discoverability, > > > interface, registration method (through annotations and build time > > > processing? /META-INF/services? other?)? > > > > It's OSGi services. > > > > > > > > 2. Removing Pax + hiding OSGi seems complementary, but is OSGi going to > > be > > > implementation detail of Karaf 5? or just deployment method (Minho / > > Felix > > > Atomos?) If you say that pax-web will still be available, it means it > > needs > > > full OSGi runtime (Felix, Equinox) underneath. Mind that the biggest > > > obstacle when refactoring Pax Web 7 into Pax Web 8 was this entire > > > "discoverability" mechanism, which allows you to scan > > > bundles/fragments/wires looking for annotated web elements, SCIs and > > > web-fragment.xml files... So if you hide OSGi under "Karaf services" and > > at > > > the same time keep OSGi for those who want it, it'd be (sorry for > > analogy) > > > like hiding an elephant under a napkin... :) > > > > Fair comment. The purpose of Karaf Services is to simplify and focus > > only on what matters for the users in the Karaf context. > > For instance, why not just supporting Servlet OSGi services listening, > > not need to support annotation web elements or web-fragments.xml. > > If a user wants these features, then it will use Pax Web. > > But, if the user just need a simple webcontainer for servlet and Karaf > > webconsole, then Karaf Web service would be enough. > > > > > > > > 3. Pax URL and Pax Web accept configuration via ConfigAdmin. So again - > > you > > > can't remove, you have to hide it (see #2). > > > > I'm not too concerned about ConfigAdmin: it will stay there. > > > > > > > > 4. Also for Pax Web - it required a lot of effort to make it > > "restartabl
Re: [PROPOSAL] Apache Karaf runtime releases and roadmap
Hi Grzegorz Thanks for your message, it's highly appreciated. See my comments inline: > 1. What exactly are "Karaf services"? Are these OSGi services? (registered > with BundleContext.registerService(iface, object, properties)?) If not then > what are the aspects that make them "services" - discoverability, > interface, registration method (through annotations and build time > processing? /META-INF/services? other?)? It's OSGi services. > > 2. Removing Pax + hiding OSGi seems complementary, but is OSGi going to be > implementation detail of Karaf 5? or just deployment method (Minho / Felix > Atomos?) If you say that pax-web will still be available, it means it needs > full OSGi runtime (Felix, Equinox) underneath. Mind that the biggest > obstacle when refactoring Pax Web 7 into Pax Web 8 was this entire > "discoverability" mechanism, which allows you to scan > bundles/fragments/wires looking for annotated web elements, SCIs and > web-fragment.xml files... So if you hide OSGi under "Karaf services" and at > the same time keep OSGi for those who want it, it'd be (sorry for analogy) > like hiding an elephant under a napkin... :) Fair comment. The purpose of Karaf Services is to simplify and focus only on what matters for the users in the Karaf context. For instance, why not just supporting Servlet OSGi services listening, not need to support annotation web elements or web-fragments.xml. If a user wants these features, then it will use Pax Web. But, if the user just need a simple webcontainer for servlet and Karaf webconsole, then Karaf Web service would be enough. > > 3. Pax URL and Pax Web accept configuration via ConfigAdmin. So again - you > can't remove, you have to hide it (see #2). I'm not too concerned about ConfigAdmin: it will stay there. > > 4. Also for Pax Web - it required a lot of effort to make it "restartable". > I mean even Tomcat/Jetty/Undertow itself keep each webapp in separate > classloader, so you can kind of get rid of the webapp (undeploy) if you > like. Pax Web pushes this to the extreme with whiteboard, where you can > have filters from different bundles filtering access to servlets from > different bundles and sending events to listeners from yet different > bundles and everything is (should be) classloader-safe. Hinding it under > non-hierarchical classloader may not be possible... Same here: restartable could be Pax Web feature. > > 5. You've mentioned "main focus on Tomcat", but roughly speaking, Tomcat > operates on entire webapps. It's only Pax Web (or Felix HTTP with Jetty) > that make it possible to operate on the level of single > servlet/filter/listener/SCI/... - how could such "Karaf web service for > Tomcat" look like if you, say, wanted to register a servlet + filter? How > would you package and register such servlet + filter? Tomcat for the Karaf Web service yes (not strong opinion here, it would be Jetty). And as state earlier, only Servlet/Filter service registration package will be supported. The purpose is not to remove Pax * projects, it's more to have very simple "native" Karaf services. Regards JB > > Not that I don't approve the plans (I like how you think about the future), > or maybe simply my mind went numb after working for few weeks with > rollup.js and typescript, but I don't feel like I can provide any > constructive feedback besides asking for clarification... > > kind regards > Grzegorz Grzybek > > wt., 11 cze 2024 o 16:20 Matt Pavlovich napisał(a): > > > Hi JB- > > > > Makes sense, I figured I’d make the pitch for the pax-* merger in that > > there is a lot of good use cases, stability and performance scenarios > > already handled there. > > > > I look forward to assisting with the new karaf-* services. > > > > Thanks, > > Matt Pavlovich > > > > > On Jun 11, 2024, at 3:45 AM, Jean-Baptiste Onofré > > wrote: > > > > > > Hi all, > > > > > > I would like to clarify the PAX * questions. It would be still > > > possible to use PAX * projects in Karaf 5.x, via the features (as > > > today), but optional (not boot features anymore). > > > > > > As an alternative, we will have opinionated Karaf services features. > > > > > > For instance, pax-web will still be available (if people want to use > > > it), but Karaf will provide a web feature (as alternative). > > > > > > For URL and logging, Karaf will provide simplified mvn and wrap url > > > handlers, and opinionated Karaf logging service (only supporting slf4j > > > and log4j2). If users still want to use Pax URL
Re: [PROPOSAL] Apache Karaf runtime releases and roadmap
Hi all, I would like to clarify the PAX * questions. It would be still possible to use PAX * projects in Karaf 5.x, via the features (as today), but optional (not boot features anymore). As an alternative, we will have opinionated Karaf services features. For instance, pax-web will still be available (if people want to use it), but Karaf will provide a web feature (as alternative). For URL and logging, Karaf will provide simplified mvn and wrap url handlers, and opinionated Karaf logging service (only supporting slf4j and log4j2). If users still want to use Pax URL and Pax Logging, they will still be able to do so via custom distribution. The reasons to provide Karaf opinionated services are: 1. Karaf services are governed by the ASF rule, as Karaf, which is not the case for Pax 2. Pax * projects are great as "generic" OSGi services. On the other hand, it brings some complexity to be abstract enough for OSGi use cases and compliant with the OSGi specs. Karaf services will really be Karaf centric, not necessarily respecting the OSGi specs, but focusing on users' needs. 3. Facilitate Karaf tooling around to improve the developer experience. Regards JB On Tue, Jun 11, 2024 at 8:48 AM Francois Papon wrote: > > Hi Serge, > > You can already build a static Karaf custom definition ready to start > without downloading all the dependencies at startup and create a docker > image with that. > > The most complex part with GraalVM in our case is all the 3rd party > dependencies and the OSGi framework. I'm afraid that it will not be > possible to be GraalVM compatible. > > I'm not sure to understand your thoughts about "full OSGi for dev", what > to you mean? > > regards, > > François > > On 08/06/2024 08:31, Serge Huber wrote: > > Hi François, > > > > I understand not everything has to be native, but for example for Apache > > Unomi the default deployment is now mostly in containers, and extensions > > are usually deployed mostly in development environments and then statically > > packaged for production deployments. > > > > Having the option to then use Karaf 5 to leverage the benefits of GraalVM > > Native Image would be very interesting I believe. I think other > > applications might be interested in these types of scenarios: full OSGi for > > development, maybe pre-production and testing, and possibility to have a > > more « static » deployment for production that could be compatible with > > native image. > > > > WDYT ? > > > > Regards, > > Serge… > > > > Le jeu. 6 juin 2024 à 11:09, Francois Papon > > a écrit : > > > >> Hi Serge, > >> > >> I don't think there is a benefit about GraalVM for long running process > >> like Karaf. All java things doesn't need to be GraalVM native :) > >> > >> Another problem is that the community edition of GraalVM doesn't bring > >> all the improvement as the commercial one (GC, PGO...) > >> > >> regards, > >> > >> François > >> > >> On 05/06/2024 15:13, Serge Huber wrote: > >>> Hi JB thanks for the proposal, > >>> > >>> Sounds great to me. For me Karaf 5 should really be a natural fit for > >>> containerized deployments, making it super easy to package applications > >>> that can then easily be scaled up (and down), so making it more > >> predictable > >>> and possibly more static can be a good thing. > >>> > >>> Is a goal also to make it compatible with GraalVM Native Image ? > >>> > >>> Best regards, > >>> Serge. > >>> > >>> On Tue, Jun 4, 2024 at 11:18 AM Jean-Baptiste Onofré > >>> 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 > >>>> >
Re: [PROPOSAL] Apache Karaf runtime releases and roadmap
Hi Serge, GraalVM Native is interesting, but keeping the OSGi internals it will be a bit challenging (especially regarding reflections). I don't say it's impossible, but it's more work/challenges. Regards JB On Wed, Jun 5, 2024 at 3:13 PM Serge Huber wrote: > > Hi JB thanks for the proposal, > > Sounds great to me. For me Karaf 5 should really be a natural fit for > containerized deployments, making it super easy to package applications > that can then easily be scaled up (and down), so making it more predictable > and possibly more static can be a good thing. > > Is a goal also to make it compatible with GraalVM Native Image ? > > Best regards, > Serge. > > On Tue, Jun 4, 2024 at 11:18 AM Jean-Baptiste Onofré > 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 > >
Re: [PROPOSAL] Apache Karaf runtime releases and roadmap
Hi To be clear about Karaf 4.5.0: the plan is not to change the internals. You will still be able to use OSGi specs / services. The main proposed change is to simplify the services in Karaf mostly for the pax * parts. There are two main reasons about that : - having Karaf provided services would simplify the releases, dependency management and security due diligence - some pax components are very complex and we can have a simpler impl (and maintainable) with Karaf opiniated service Specifically about pax web, it doesn’t mean necessary to not super OSGi web spec. It’s mainly to focus on tomcat and Karaf impl as part of the Karaf project. I hope it helps regards JB Le mer. 5 juin 2024 à 07:06, Bernd Eckenfels a écrit : > I am looking forward to a lighter solution if it > Brings us JakartaEE and less overhead. > > However there is a lot of flexibility and work in > those PAX projects, you sure you can replicate > them? > > (Things like providing and configuring all > common logging Fassaden are just one of the > perks we like about Karaf) > > Also when you say PAX Exam replacement, will you still provide the test > APIs to setup framework and bundles and how does that affect the runtime. > Or maybe the other way around - does that only affect how Karaf 5 is tested > but not what users will use? > > (BTW I was not following closely, is this „karaf 5“ then the new named > runtime or a step in between? I’d there still a Codename for it? > > Personally speaking I am not happy about > migrating to a new environment, If I would be I > might as well consider spring boot or one of the > micro service projects with big econsystens - especially if even the Felix > and PAX Ecosystem > no longer would be first class providers) > > The 447/45 plans sound great, though. > > Gruß > Bernd > > > fpapon wrote on 5. June 2024 06:46 (GMT +02:00): > > > Hi, > > > > I already discuss with JB (at community over code Bratislava) about > > these points so I have nothing to add :) > > > > Just keeping in mind that we want to have a lighter project for the > > maintainability and abstract the OSGi complexity. > > > > regards, > > > > François > > > > On 04/06/2024 11:17, Jean-Baptiste Onofré 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 > > > > -- > > -- > > François > > > > > > > Gruß > Bernd > — > https://bernd.eckenfels.net >
[PROPOSAL] Apache Karaf runtime releases and roadmap
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
Re: Apache Karaf board report for June 24
Hey François, Good idea, I updated the report accordingly. Thanks, Regards JB On Wed, May 29, 2024 at 9:28 PM Francois Papon wrote: > > Hi JB, > > LGTM > > May be we can also add in the camel-karaf integration the direct-vm > add-on that are not a part of camel core anymore and is very usefull in > Karaf context. > > regards, > > François > > On 29/05/2024 15:54, Jean-Baptiste Onofré wrote: > > Hi folks, > > > > I prepared the board report for June 24: > > > > https://cwiki.apache.org/confluence/display/KARAF/Board+Reports > > > > Please take a look and feel free to update the report. > > I plan to submit the report asap. > > > > Thanks ! > > Regards > > JB
Apache Karaf board report for June 24
Hi folks, I prepared the board report for June 24: https://cwiki.apache.org/confluence/display/KARAF/Board+Reports Please take a look and feel free to update the report. I plan to submit the report asap. Thanks ! Regards JB
[RESULT][VOTE] Apache Karaf OSGi runtime 4.4.6 release
Hi folks, This vote passed with the following result: +1 (binding): Grzegorz Grzybek, Achim Nierbeck, JB Onofré, François Papon, Jamie Goodyear +1 (non binding): Matt Pavlovich, Steinar Bang, Robert Varga, Romain Manni-Bucau, Jakub Herkel I'm promoting the artifacts on Maven Central and dist.apache.org. I will update Jira and the website, then I will send the announcement. Thanks all for your vote! Regards JB On Tue, Apr 9, 2024 at 3:33 PM Jean-Baptiste Onofré wrote: > > Hi folks, > > I submit Apache Karaf OSGi runtime 4.4.6 release to your vote. > > This release is a maintenance release on the 4.4.x series bringing > fixes and dependency updates, especially: > - new Spring 6.x features (NB: you would need Java 17+ to use it) > - Upgrade to Pax Web 8.0.27 / Jetty 9.4.54.v20240208 > - Upgrade to Bouncycastle 1.77 > - Upgrade to sshd 2.12.1 > - and much more! > > You can take a look on the Release Notes for details: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12354057 > > Maven Staging Repository: > https://repository.apache.org/content/repositories/orgapachekaraf-1191/ > > Dist Staging Repository: > https://dist.apache.org/repos/dist/dev/karaf/4.4.6/ > > Git tag: > karaf-4.4.6 > > Please vote to approve this release: > [ ] +1 Approve the release > [ ] -1 Don't approve the release (please provide specific comments) > > This vote will be open for at least 72 hours. > > Regards > JB
Re: [VOTE] Apache Karaf OSGi runtime 4.4.6 release
+1 (binding) Regards JB On Tue, Apr 9, 2024 at 3:33 PM Jean-Baptiste Onofré wrote: > > Hi folks, > > I submit Apache Karaf OSGi runtime 4.4.6 release to your vote. > > This release is a maintenance release on the 4.4.x series bringing > fixes and dependency updates, especially: > - new Spring 6.x features (NB: you would need Java 17+ to use it) > - Upgrade to Pax Web 8.0.27 / Jetty 9.4.54.v20240208 > - Upgrade to Bouncycastle 1.77 > - Upgrade to sshd 2.12.1 > - and much more! > > You can take a look on the Release Notes for details: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12354057 > > Maven Staging Repository: > https://repository.apache.org/content/repositories/orgapachekaraf-1191/ > > Dist Staging Repository: > https://dist.apache.org/repos/dist/dev/karaf/4.4.6/ > > Git tag: > karaf-4.4.6 > > Please vote to approve this release: > [ ] +1 Approve the release > [ ] -1 Don't approve the release (please provide specific comments) > > This vote will be open for at least 72 hours. > > Regards > JB
[VOTE] Apache Karaf OSGi runtime 4.4.6 release
Hi folks, I submit Apache Karaf OSGi runtime 4.4.6 release to your vote. This release is a maintenance release on the 4.4.x series bringing fixes and dependency updates, especially: - new Spring 6.x features (NB: you would need Java 17+ to use it) - Upgrade to Pax Web 8.0.27 / Jetty 9.4.54.v20240208 - Upgrade to Bouncycastle 1.77 - Upgrade to sshd 2.12.1 - and much more! You can take a look on the Release Notes for details: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12354057 Maven Staging Repository: https://repository.apache.org/content/repositories/orgapachekaraf-1191/ Dist Staging Repository: https://dist.apache.org/repos/dist/dev/karaf/4.4.6/ Git tag: karaf-4.4.6 Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Don't approve the release (please provide specific comments) This vote will be open for at least 72 hours. Regards JB
[HEADS UP] Apache Karaf runtime 4.4.6 release will be on vote tomorrow
Hi folks, All is OK for the Karaf runtime 4.4.6 release. I only have one issue introduced by the Apache POM 31 update on the release profile. I'm fixing this now. I will submit the release to vote just after. Stay tuned! Regards JB
[PROPOSAL] Apache Karaf 4.5.x with Java 17+
Hi folks, I'm preparing the Karaf 4.4.6 release using Java 11+. It will provide Spring 6.x features requiring Java 17. As Karaf 4.4.x still uses Camel 3.2.x (Java 11+), it will be up to the user to choose Java 11 (with Camel working) or Java 17+ (with Spring working). With the effort ongoing for camel-karaf 4.x (with Java 17+ support), I propose to target Karaf 4.5.x to Java 17+ and remove support of Java 11. If it's OK for you, I will update Jenkinsfile to use Java 17 by default on main (instead of Java 11 today), and update the resources to target Java 17. Thoughts ? Regards JB
Re: [HEADS UP] Apache Karaf runtime 4.4.5 release
Yes, it's planned: I'm preparing the ServiceMix Bundles release to be able to update in Karaf. That's actually one of the reasons why I had to postpone the Karaf release. Regards JB On Wed, Mar 27, 2024 at 12:00 PM Steven Huypens wrote: > > Hi JB, > > When are you planning to upgrade Spring Security from 5.7.3 to 5.7.12 ? > > Best regards, > Steven > > On Sun, Mar 24, 2024 at 7:04 PM Jean-Baptiste Onofré > wrote: > > > Hi guys, > > > > New update about 4.4.5 and 4.5.0 releases. > > > > I think I fixed all found issues (and dependency updates). > > I'm now opening the PRs, and I will submit the releases to vote in the > > coming days. > > > > Thanks for your patience, > > > > Regards > > JB > > > > On Mon, Feb 19, 2024 at 8:21 AM Jean-Baptiste Onofré > > wrote: > > > > > > Hi guys, > > > > > > While working on Camel 4.x support (4.4.0) in Karaf 4.x, I identified > > > some issues and required improvements. > > > > > > I'm working on this: I would like to include this in the Karaf 4.5.0 > > > release as it will be a better experience for our users (with a > > > cleaner Camel 4.x and ActiveMQ 6.x support). > > > > > > I will keep you posted. > > > > > > Regards > > > JB > > > > > > On Mon, Dec 18, 2023 at 1:54 PM Jean-Baptiste Onofré > > wrote: > > > > > > > > Hi guys, > > > > > > > > I'm finalizing Karaf runtime 4.4.5 release preparation. > > > > I should be able to submit the release to vote just around Christmas. > > > > > > > > I will keep you posted. > > > > > > > > Regards > > > > JB > >
Re: [HEADS UP] Apache Karaf runtime 4.4.5 release
Thanks for new Pax Web releases ! I will do the updates. Regards JB On Mon, Mar 25, 2024 at 7:26 AM Grzegorz Grzybek wrote: > > Hello > > I've recently released Pax Web versions with runtime upgrades (and one fix), > but I see there's already new Undertow and Tomcat. I'll release new version > of Pax Web today - WDYT? > > regards > Grzegorz Grzybek > > niedz., 24 mar 2024 o 19:04 Jean-Baptiste Onofré > napisał(a): >> >> Hi guys, >> >> New update about 4.4.5 and 4.5.0 releases. >> >> I think I fixed all found issues (and dependency updates). >> I'm now opening the PRs, and I will submit the releases to vote in the >> coming days. >> >> Thanks for your patience, >> >> Regards >> JB >> >> On Mon, Feb 19, 2024 at 8:21 AM Jean-Baptiste Onofré >> wrote: >> > >> > Hi guys, >> > >> > While working on Camel 4.x support (4.4.0) in Karaf 4.x, I identified >> > some issues and required improvements. >> > >> > I'm working on this: I would like to include this in the Karaf 4.5.0 >> > release as it will be a better experience for our users (with a >> > cleaner Camel 4.x and ActiveMQ 6.x support). >> > >> > I will keep you posted. >> > >> > Regards >> > JB >> > >> > On Mon, Dec 18, 2023 at 1:54 PM Jean-Baptiste Onofré >> > wrote: >> > > >> > > Hi guys, >> > > >> > > I'm finalizing Karaf runtime 4.4.5 release preparation. >> > > I should be able to submit the release to vote just around Christmas. >> > > >> > > I will keep you posted. >> > > >> > > Regards >> > > JB
Re: [HEADS UP] Apache Karaf runtime 4.4.5 release
Hi guys, New update about 4.4.5 and 4.5.0 releases. I think I fixed all found issues (and dependency updates). I'm now opening the PRs, and I will submit the releases to vote in the coming days. Thanks for your patience, Regards JB On Mon, Feb 19, 2024 at 8:21 AM Jean-Baptiste Onofré wrote: > > Hi guys, > > While working on Camel 4.x support (4.4.0) in Karaf 4.x, I identified > some issues and required improvements. > > I'm working on this: I would like to include this in the Karaf 4.5.0 > release as it will be a better experience for our users (with a > cleaner Camel 4.x and ActiveMQ 6.x support). > > I will keep you posted. > > Regards > JB > > On Mon, Dec 18, 2023 at 1:54 PM Jean-Baptiste Onofré > wrote: > > > > Hi guys, > > > > I'm finalizing Karaf runtime 4.4.5 release preparation. > > I should be able to submit the release to vote just around Christmas. > > > > I will keep you posted. > > > > Regards > > JB
Re: Board report for March 2024
Thanks all ! I published the report via whimsy. Regards JB On Thu, Feb 29, 2024 at 1:45 PM Jean-Baptiste Onofré wrote: > > Hi guys, > > I prepared the board report for March 2024: > > https://cwiki.apache.org/confluence/display/KARAF/Board+Reports > > Please take a look and feel free to update. > > I would like to send the report asap. > > Thanks ! > Regards > JB
Board report for March 2024
Hi guys, I prepared the board report for March 2024: https://cwiki.apache.org/confluence/display/KARAF/Board+Reports Please take a look and feel free to update. I would like to send the report asap. Thanks ! Regards JB
Re: [HEADS UP] Apache Karaf runtime 4.4.5 release
Hi guys, While working on Camel 4.x support (4.4.0) in Karaf 4.x, I identified some issues and required improvements. I'm working on this: I would like to include this in the Karaf 4.5.0 release as it will be a better experience for our users (with a cleaner Camel 4.x and ActiveMQ 6.x support). I will keep you posted. Regards JB On Mon, Dec 18, 2023 at 1:54 PM Jean-Baptiste Onofré wrote: > > Hi guys, > > I'm finalizing Karaf runtime 4.4.5 release preparation. > I should be able to submit the release to vote just around Christmas. > > I will keep you posted. > > Regards > JB
Re: [PROPOSAL] Migrate to GitHub Issues/Actions
Hi, Yeeah, that would help. As said, my priority is the 4.5.0 release this week. The move to GH will happen after. Thanks ! Regards JB On Mon, Feb 5, 2024 at 7:33 AM Grzegorz Grzybek wrote: > > Hello > > JBO - we can discuss on slack later if you decide to migrate - we can use the > scripts I used to migrate Pax projects. > > regards > Grzegorz Grzybek > > sob., 3 lut 2024 o 06:39 Jean-Baptiste Onofré napisał(a): >> >> Hi guys, >> >> it seems we have a consensus here. >> >> I propose to complete Karaf 4.5.0 release first and then I will move >> forward on the switch to GH Issues (and also GH Actions). >> >> Thanks, >> Regards >> JB >> >> On Tue, Oct 31, 2023 at 9:27 AM Jean-Baptiste Onofré >> wrote: >> > >> > Hi guys, >> > >> > I would like to propose to move from Jira to GH Issues and from >> > Jenkins to GH Actions. >> > >> > As we have several sub-projects, each sub-project will have its own >> > space, like we do for Karaf Minho >> > (https://github.com/apache/karaf-minho). >> > >> > The migration should be "smooth" and I will work on it if you agree. >> > >> > Thoughts ? >> > >> > Regards >> > JB
Re: [PROPOSAL] Migrate to GitHub Issues/Actions
Hi guys, it seems we have a consensus here. I propose to complete Karaf 4.5.0 release first and then I will move forward on the switch to GH Issues (and also GH Actions). Thanks, Regards JB On Tue, Oct 31, 2023 at 9:27 AM Jean-Baptiste Onofré wrote: > > Hi guys, > > I would like to propose to move from Jira to GH Issues and from > Jenkins to GH Actions. > > As we have several sub-projects, each sub-project will have its own > space, like we do for Karaf Minho > (https://github.com/apache/karaf-minho). > > The migration should be "smooth" and I will work on it if you agree. > > Thoughts ? > > Regards > JB
Docker images and preparing 4.5.0 release
Hi guys, FYI, I'm updating the Karaf docker images on Docker Hub to provide multi-platform (linux/amd64 and linux/arm64) images. In the meantime, I'm resuming the 4.5.0 preparation, especially around jakarta features. I will keep you posted on that quickly. Regards JB
[ANN] Apache Karaf OSGi Runtime 4.4.5 has been released!
The Apache Karaf team is pleased to announce the Apache Karaf OSGi Runtime 4.4.5 release. Apache Karaf runtime 4.4.5 is a maintenance release, bringing a lot of dependency updates and fixes, especially: -i solate config shell commands in a dedicated bundle to avoid refresh and race condition at startup - better JDK21 support with new ASM version (9.6) - upgrade to Jetty 9.4.53.v20231009 and Pax Web 8.0.24 - upgrade to Pax Logging 2.2.6 supporting Log4j 2.22.1 and commons-logging 1.3.0 - fix webconsole plugins loading - upgrade to sshd 2.11.0 fixing ecdsa key support - ... You can take a look on the Release Notes for details: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12353604 Apache Karaf OSGi Runtime 4.4.5 is available on Maven Central or here: https://karaf.apache.org/download.html Enjoy ! The Apache Karaf team
[RESULT][VOTE] Apache Karaf OSGi runtime 4.4.5 release
Hi, this vote passed with the following result: +1 (binding): Jamie Goodyear, Grzegorz Grzybek, François Papon, Guillaume Nodet, JB Onofré +1 (non binding): Jakub Herkel, Robert Varga, Steinar Bang I'm promoting the artifacts on Maven Central and dist.apache.org, then I will update Jira and the website, and then, I will do the announcement. Thanks all for your vote ! Regards JB On Sun, Jan 7, 2024 at 7:02 PM Jean-Baptiste Onofré wrote: > > Hi guys, > > I submit Apache Karaf OSGi runtime 4.4.5 release to your vote. > > This release is a maintenance release bringing fixes and dependency > updates, especially: > - isolate config shell commands in a dedicated bundle to avoid refresh > and race condition at startup > - better JDK21 support with new ASM version (9.6) > - upgrade to Jetty 9.4.53.v20231009 and Pax Web 8.0.24 > - fix webconsole plugins loading > - upgrade to sshd 2.11.0 fixing ecdsa key support > > You can take a look on the Release Notes for details: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12353604 > > Maven Staging Repository: > https://repository.apache.org/content/repositories/orgapachekaraf-1190/ > > Dist Staging Repository: > https://dist.apache.org/repos/dist/dev/karaf/4.4.5/ > > Git tag: > karaf-4.4.5 > > Please vote to approve this release: > [ ] +1 Approve the release > [ ] -1 Don't approve the release (please provide specific comments) > > This vote will be open for at least 72 hours. > > Regards > JB
Re: [VOTE] Apache Karaf OSGi runtime 4.4.5 release
+1 (binding) Regards JB On Sun, Jan 7, 2024 at 7:02 PM Jean-Baptiste Onofré wrote: > > Hi guys, > > I submit Apache Karaf OSGi runtime 4.4.5 release to your vote. > > This release is a maintenance release bringing fixes and dependency > updates, especially: > - isolate config shell commands in a dedicated bundle to avoid refresh > and race condition at startup > - better JDK21 support with new ASM version (9.6) > - upgrade to Jetty 9.4.53.v20231009 and Pax Web 8.0.24 > - fix webconsole plugins loading > - upgrade to sshd 2.11.0 fixing ecdsa key support > > You can take a look on the Release Notes for details: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12353604 > > Maven Staging Repository: > https://repository.apache.org/content/repositories/orgapachekaraf-1190/ > > Dist Staging Repository: > https://dist.apache.org/repos/dist/dev/karaf/4.4.5/ > > Git tag: > karaf-4.4.5 > > Please vote to approve this release: > [ ] +1 Approve the release > [ ] -1 Don't approve the release (please provide specific comments) > > This vote will be open for at least 72 hours. > > Regards > JB
[VOTE] Apache Karaf OSGi runtime 4.4.5 release
Hi guys, I submit Apache Karaf OSGi runtime 4.4.5 release to your vote. This release is a maintenance release bringing fixes and dependency updates, especially: - isolate config shell commands in a dedicated bundle to avoid refresh and race condition at startup - better JDK21 support with new ASM version (9.6) - upgrade to Jetty 9.4.53.v20231009 and Pax Web 8.0.24 - fix webconsole plugins loading - upgrade to sshd 2.11.0 fixing ecdsa key support You can take a look on the Release Notes for details: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12353604 Maven Staging Repository: https://repository.apache.org/content/repositories/orgapachekaraf-1190/ Dist Staging Repository: https://dist.apache.org/repos/dist/dev/karaf/4.4.5/ Git tag: karaf-4.4.5 Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Don't approve the release (please provide specific comments) This vote will be open for at least 72 hours. Regards JB
Re: [HEADS UP] Apache Karaf runtime 4.4.5 release
Hi guys, I'm finishing https://github.com/apache/karaf/pull/1814 (just a test/classloader issue to fix) and then I will start the vote. Regards JB On Tue, Jan 2, 2024 at 11:25 AM Jean-Baptiste Onofré wrote: > > Hi guys > > I'm a bit late on this release: I plan to submit 4.4.5 to vote tonight > or tomorrow morning. > > Regards > JB > > On Mon, Dec 18, 2023 at 1:54 PM Jean-Baptiste Onofré > wrote: > > > > Hi guys, > > > > I'm finalizing Karaf runtime 4.4.5 release preparation. > > I should be able to submit the release to vote just around Christmas. > > > > I will keep you posted. > > > > Regards > > JB
Re: [HEADS UP] Apache Karaf runtime 4.4.5 release
Hi guys I'm a bit late on this release: I plan to submit 4.4.5 to vote tonight or tomorrow morning. Regards JB On Mon, Dec 18, 2023 at 1:54 PM Jean-Baptiste Onofré wrote: > > Hi guys, > > I'm finalizing Karaf runtime 4.4.5 release preparation. > I should be able to submit the release to vote just around Christmas. > > I will keep you posted. > > Regards > JB
[HEADS UP] Apache Karaf runtime 4.4.5 release
Hi guys, I'm finalizing Karaf runtime 4.4.5 release preparation. I should be able to submit the release to vote just around Christmas. I will keep you posted. Regards JB
Re: Board report for December 2023
Hi Willem We had a discussion: https://lists.apache.org/thread/nv3f783vj0kc0wnj39t039qjqz0fcjmb It was a year ago, with a lazy consensus :) However, I think I didn't start a formal vote. I will. Regards JB On Mon, Dec 18, 2023 at 8:02 AM Willem Ning Jiang wrote: > > Hi JB > > I just have a quick question for this part > “Following the vote, Karaf Cave and Karaf Winegrower have been removed from > the mailing list.” > Could you show me the link of Vote ? I cannot find any mail thread in these > three month dev mailing list. > > Thanks, > > Willem > > On 2023/12/15 12:42:21 Jean-Baptiste Onofré wrote: > > Hi guys, > > > > I'm sorry, we are late for the board report this month (I didn't > > receive a reminder and forgot to create one). > > So I quickly created a board report here: > > > > https://cwiki.apache.org/confluence/display/KARAF/Board+Reports > > > > Please take a look, I would like to send it asap (if possible tonight). > > > > Thanks ! > > Regards > > JB > >
Re: Board report for December 2023
Thanks all, I just submitted the report. Regards JB On Fri, Dec 15, 2023 at 1:42 PM Jean-Baptiste Onofré wrote: > > Hi guys, > > I'm sorry, we are late for the board report this month (I didn't > receive a reminder and forgot to create one). > So I quickly created a board report here: > > https://cwiki.apache.org/confluence/display/KARAF/Board+Reports > > Please take a look, I would like to send it asap (if possible tonight). > > Thanks ! > Regards > JB
Board report for December 2023
Hi guys, I'm sorry, we are late for the board report this month (I didn't receive a reminder and forgot to create one). So I quickly created a board report here: https://cwiki.apache.org/confluence/display/KARAF/Board+Reports Please take a look, I would like to send it asap (if possible tonight). Thanks ! Regards JB
Re: Karaf 4.4.4 and OpenJdk 21
25) > ~[?:?] > ... 27 more > > But when I run on OpenJDK 17 it works fine. Is this due to the problem you > mentioned regarding Aries Blueprint/Proxy? It looks like ASM is being used. > However Karaf 4.4.4 uses ASM 9.5 which should support OpenJDK 21. > > I thought that generally a new Java version is backwards compatible. > Meaning that a specific java runtime would handle classes compiled for an > older java version. In this case, if I compile for java 17 I should be able > to run in on a java runtime >= 17. But this does not seem to be the case... > > /Bengt > > Den mån 27 nov. 2023 kl 17:31 skrev Bengt Rodehav : > > > Thanks for the quick reply, > > > > /Bengt > > > > Den mån 27 nov. 2023 kl 15:16 skrev Jean-Baptiste Onofré > >: > > > >> Hi > >> > >> Karaf almost but not third parties (Aries Blueprint/Proxy, etc). > >> > >> I'm starting Karaf 4.5.x with full JDK21 support. > >> > >> Thanks ! > >> Regards > >> JB > >> > >> On Mon, Nov 27, 2023 at 1:50 PM Bengt Rodehav wrote: > >> > > >> > Does Karaf 4.4.4 work with OpenJdk 21? > >> > > >> > /Bengt > >> > >
Re: Building Karaf 4.4.4
That's probably the issue. Let me try to reproduce on a Windows VM. I will keep you posted. Regards JB On Mon, Nov 27, 2023 at 5:32 PM Bengt Rodehav wrote: > > I'm building on Windows. > > /Bengt > > Den mån 27 nov. 2023 kl 15:18 skrev Jean-Baptiste Onofré : > > > Hi, > > > > winsw is part of the base feature. > > > > Are you building on Windows or Unix ? > > > > Regards > > JB > > > > On Mon, Nov 27, 2023 at 1:22 PM Bengt Rodehav wrote: > > > > > > I have downloaded the source distribution of Karaf 4.4.4. When building I > > > get the following error message: > > > > > > Could not find artifact com.sun.winsw:winsw:exe:net4:2.3.0 > > > > > > I can't find this artifact in Maven central (only older versions). Also, > > I > > > googled this and found the following project in Github: > > > https://github.com/winsw/winsw > > > > > > But it seems to be for .NET, not for java. > > > > > > Can anyone explain this and point me to where I can download the > > necessary > > > dependency? > > > > > > /Bengt > >
Re: Building Karaf 4.4.4
Hi, winsw is part of the base feature. Are you building on Windows or Unix ? Regards JB On Mon, Nov 27, 2023 at 1:22 PM Bengt Rodehav wrote: > > I have downloaded the source distribution of Karaf 4.4.4. When building I > get the following error message: > > Could not find artifact com.sun.winsw:winsw:exe:net4:2.3.0 > > I can't find this artifact in Maven central (only older versions). Also, I > googled this and found the following project in Github: > https://github.com/winsw/winsw > > But it seems to be for .NET, not for java. > > Can anyone explain this and point me to where I can download the necessary > dependency? > > /Bengt
Re: Karaf 4.4.4 and OpenJdk 21
Hi Karaf almost but not third parties (Aries Blueprint/Proxy, etc). I'm starting Karaf 4.5.x with full JDK21 support. Thanks ! Regards JB On Mon, Nov 27, 2023 at 1:50 PM Bengt Rodehav wrote: > > Does Karaf 4.4.4 work with OpenJdk 21? > > /Bengt
[INFO] New train of releases
Hi guys, Now that ActiveMQ 6.0.0 has been released, I'm back on Karaf. I'm preparing two new releases: - 4.4.5 with fixes and dependencies update - 4.5.0 with new features resolver/service (optional), new specs and Jakarta namespace support 4.4.5 will be submitted to vote soon (probably next week). About 4.5.0, I target to submit to vote before Christmas. On the other hand, I'm also resuming work on Decanter and Cellar. I will keep you posted. Regards JB
Re: [PROPOSAL] Migrate to GitHub Issues/Actions
Hi guys Any comments on that one ? If there are no objections, I will move forward with that. Regards JB On Tue, Oct 31, 2023 at 9:27 AM Jean-Baptiste Onofré wrote: > > Hi guys, > > I would like to propose to move from Jira to GH Issues and from > Jenkins to GH Actions. > > As we have several sub-projects, each sub-project will have its own > space, like we do for Karaf Minho > (https://github.com/apache/karaf-minho). > > The migration should be "smooth" and I will work on it if you agree. > > Thoughts ? > > Regards > JB
Re: Karaf + SOAP + JDK 21
Hi Which CXF version are you using ? I guess it’s about CXF support. I will check on main. Regards JB Le dim. 5 nov. 2023 à 20:31, Mark Derricutt a écrit : > Anyone got Karaf 4.4.4 and SOAP working under JDk 21? > > I've been trying to update our project from Java 8, and just getting hit > with the lack of javax.ws.* classes being a part of the JDK from 9 onward. > > Even the stock Karaf SOAP example doesn't seem to work for me - I'm > guessing I just need to add an extra dependency which provides those > classes, but haven't been able to find a recommended/standard > implementation to use... > > Any pointers? > > > >
Releases preparation
Hi guys You might have seen I was pretty quiet recently. We have been hit by Ciaran storm. I don’t have electricity and Internet connection at home. As we have important damages on the house, we decided to rent a new house for a few days. I will be back online tonight and I will resume Karaf releases preparation tomorrow. Sorry for the delay. Regards
Re: [PROPOSAL] Migrate to GitHub Issues/Actions
There's no problem from ASF standpoint: - INFRA delegated the settings to .asf.yml - several ASF projects already use GH Issues/Actions (Iceberg, ...) - we already have Karaf Minho using it https://infra.apache.org/github-actions-policy.html Regards JB On Tue, Oct 31, 2023 at 9:31 AM Grzegorz Grzybek wrote: > > Hello > > Technically it's easy - I wrote and successfully used > https://github.com/ops4j/org.ops4j.tools/tree/main/jira2github to migrate > Pax projects from Jira to GitHub. > > But how does it relate to ASF governance? > > regards > Grzegorz Grzybek > > wt., 31 paź 2023 o 09:27 Jean-Baptiste Onofré napisał(a): > > > Hi guys, > > > > I would like to propose to move from Jira to GH Issues and from > > Jenkins to GH Actions. > > > > As we have several sub-projects, each sub-project will have its own > > space, like we do for Karaf Minho > > (https://github.com/apache/karaf-minho). > > > > The migration should be "smooth" and I will work on it if you agree. > > > > Thoughts ? > > > > Regards > > JB > >
[PROPOSAL] Migrate to GitHub Issues/Actions
Hi guys, I would like to propose to move from Jira to GH Issues and from Jenkins to GH Actions. As we have several sub-projects, each sub-project will have its own space, like we do for Karaf Minho (https://github.com/apache/karaf-minho). The migration should be "smooth" and I will work on it if you agree. Thoughts ? Regards JB
Re: [UPDATE] Karaf WebConsole has issues with Karaf 4.4.4
Yes, it's planned as part of the dependency updates process. Thanks, Regards JB On Wed, Oct 18, 2023 at 12:59 PM Jakub Herkel wrote: > > Hello, > > Could you also update bouncycastle to version 1.76 for Karaf 4.4.5? > > with best regards > > Jakub Herkel > > > > On Wed, Oct 18, 2023 at 9:36 AM Grzegorz Grzybek wrote: > > > > Hello > > > > A little updated - because of CVE-2023-44487 (HTTP/2 rapid reset attack) I > > was waiting for updates to Undertow, Jetty and Tomcat. Undertow has been > > released few hours ago, so I'm releasing new Pax Web today. > > But I found new version of Log4j2 (2.21.0) and I'm releasing Pax Logging > > first. > > > > kind regards > > Grzegorz Grzybek > > > > śr., 18 paź 2023 o 07:43 Jean-Baptiste Onofré > > napisał(a): > >> > >> Hey guys > >> > >> As we have new pax web releases now, I’m resuming fixes and upgrade in > >> preparation for releases. > >> > >> Regards > >> JB > >> > >> Le dim. 1 oct. 2023 à 18:39, Jean-Baptiste Onofré a > >> écrit : > >>> > >>> Hi Robert > >>> > >>> Sure, I will (I have other stuff to include anyway :)). > >>> > >>> Regards > >>> JB > >>> > >>> On Sun, Oct 1, 2023 at 8:32 AM Robert Varga wrote: > >>> > > >>> > Hey JB,Can you also look at including aries-proxy-1.1.14? It needs the > >>> > usual ASM bump to not fail when run on Java 21.Thanks,Robert Sent from > >>> > my Galaxy > >>> > Original message From: Jean-Baptiste Onofré > >>> > Date: 10/1/23 07:33 (GMT+01:00) To: dev > >>> > , user Subject: [UPDATE] > >>> > Karaf WebConsole has issues with Karaf 4.4.4 Hi guys,I created > >>> > https://issues.apache.org/jira/browse/KARAF-7769Since the Felix > >>> > WebConsole update, the Karaf WebConsole plugins(features, gogo, ...) > >>> > don't load correctly.I'm fixing that and I will quickly submit Karaf > >>> > 4.4.5 to vote.Sorry for the inconvenience;RegardsJB
Re: [UPDATE] Karaf WebConsole has issues with Karaf 4.4.4
Hey guys As we have new pax web releases now, I’m resuming fixes and upgrade in preparation for releases. Regards JB Le dim. 1 oct. 2023 à 18:39, Jean-Baptiste Onofré a écrit : > Hi Robert > > Sure, I will (I have other stuff to include anyway :)). > > Regards > JB > > On Sun, Oct 1, 2023 at 8:32 AM Robert Varga wrote: > > > > Hey JB,Can you also look at including aries-proxy-1.1.14? It needs the > usual ASM bump to not fail when run on Java 21.Thanks,Robert Sent from my > Galaxy > > ---- Original message From: Jean-Baptiste Onofré < > j...@nanthrax.net> Date: 10/1/23 07:33 (GMT+01:00) To: dev < > dev@karaf.apache.org>, user Subject: [UPDATE] > Karaf WebConsole has issues with Karaf 4.4.4 Hi guys,I created > https://issues.apache.org/jira/browse/KARAF-7769Since the Felix > WebConsole update, the Karaf WebConsole plugins(features, gogo, ...) don't > load correctly.I'm fixing that and I will quickly submit Karaf 4.4.5 to > vote.Sorry for the inconvenience;RegardsJB >
Re: [UPDATE] Karaf WebConsole has issues with Karaf 4.4.4
Hi Robert Sure, I will (I have other stuff to include anyway :)). Regards JB On Sun, Oct 1, 2023 at 8:32 AM Robert Varga wrote: > > Hey JB,Can you also look at including aries-proxy-1.1.14? It needs the usual > ASM bump to not fail when run on Java 21.Thanks,Robert Sent from my Galaxy > Original message ----From: Jean-Baptiste Onofré > Date: 10/1/23 07:33 (GMT+01:00) To: dev > , user Subject: [UPDATE] Karaf > WebConsole has issues with Karaf 4.4.4 Hi guys,I created > https://issues.apache.org/jira/browse/KARAF-7769Since the Felix WebConsole > update, the Karaf WebConsole plugins(features, gogo, ...) don't load > correctly.I'm fixing that and I will quickly submit Karaf 4.4.5 to vote.Sorry > for the inconvenience;RegardsJB
[UPDATE] Karaf WebConsole has issues with Karaf 4.4.4
Hi guys, I created https://issues.apache.org/jira/browse/KARAF-7769 Since the Felix WebConsole update, the Karaf WebConsole plugins (features, gogo, ...) don't load correctly. I'm fixing that and I will quickly submit Karaf 4.4.5 to vote. Sorry for the inconvenience; Regards JB
Re: The meaning of karaf-bom
Hi, I like the proposal of having different BOMs different of the use (for instance Quarkus has two different boms: one for application, one for test). I can definitely create a bom module containing: - bom/stack - bom/application If it works for you, I can create a Jira and then prepare this for Karaf 4.5.0. Thoughts ? Regards JB On Wed, Sep 27, 2023 at 9:46 PM Steven Huypens wrote: > > Hi Robert, > > Thank you for clarifying the difference between both BOMs. I believe that > the current Karaf BOM incorporates elements from both types, whereas you > only require the library BOM. > > In my opinion, it would be beneficial to create a distinct stack BOM. This > approach would enhance clarity for consumers. Additionally, by > consolidating all Maven version properties within this 'stack BOM,' > projects utilizing Karaf could easily synchronize their dependency versions > with those of Karaf, without the need to reference the entire Karaf parent > POM. > > > Kind regards, > Steven > > On Wed, Sep 27, 2023 at 5:18 PM Robert Varga wrote: > > > On 27/09/2023 08.35, Jean-Baptiste Onofré wrote: > > > Hi > > > > Hello, > > > > > Not really imho : each project does the way it considers the best. > > > > > > For instance, quarkus is using a bop approach similar to Karaf: it > > exposes > > > all dependencies in the BOM as a guarantee about the versions working > > fine. > > > > > > The idea in Karaf bom is to clearly state the versions verified in Karaf. > > > Users can always override the versions, but the BOM guarantees the > > > qualified versions. > > > > Right, and nowadays there are lot more BOM-related resources on the web. > > > > Researching what Maven4 will do (for the other email), I came across > > this: https://www.infoq.com/news/2023/06/maven-puzzlers-devoxxuk/ > > > > Which makes a distinction, making both our views correct: > > > > > The library BOM - defines projects that are related to a single > > library. For example, the JUnit or Jackson BOM defines everything related > > to JUnit and nothing more > > > The stack BOM - Spring or Quarkus BOM bring all dependencies of > > various projects required for the given project to function. Each BOM > > contains a combination of versions that work best together > > > > I meant to former while Karaf is doing the latter. Count myself educated :) > > > > It might make sense to somehow also provide just a library BOM, but I > > struggle to define the use case where I would really need it :) > > > > Thanks, > > Robert > > > > > > > > > > Regards > > > JB > > > > > > Le dim. 24 sept. 2023 à 22:54, Robert Varga a écrit : > > > > > >> Hello, > > >> > > >> One thing that strikes me is "Bill of Materials" as perceived by > > karaf-bom. > > >> > > >> As it currently stands, karaf-bom includes all declarations of > > >> karaf.git/pom.xml. > > >> > > >> As I understand the bill-of-materials concept under Maven, it should > > >> only list artifacts provided by a particular project, nothing more, > > >> nothing less. > > >> > > >> In the latter regard, we should be only declaring org.apache.karaf > > >> artifacts in karaf-bom. > > >> > > >> From a downstream's perspective, there is a difference between > > >> importing karaf-bom (in which case the downstream takes the > > >> resposibility to align any shared depdendencies) and karaf.git/pom.xml > > >> (in which case I am trusting Karaf with a ton of dependencies). > > >> > > >> Currently, there is no distinction between those two. > > >> > > >> Is it fair to align karaf-bom with the above expectation (and hence not > > >> leak things like org.slfj4.api's version)? > > >> > > >> As it stands there is no distinction, with this proposal current > > >> downstreams wishing to retain current state would scope=import > > >> karaf.git/pom.xml instead of karaf-bom (a change of maven coordinates) > > >> with no otherwise-observable change. > > >> > > >> Does this make sense? > > >> > > >> Regards, > > >> Robert > > >> > > > > >
Re: Questions about KARAF-5680
Hi Robert, Thanks ! I will take a look. Regards JB On Wed, Sep 27, 2023 at 6:29 PM Robert Varga wrote: > > On 27/09/2023 08.32, Jean-Baptiste Onofré wrote: > > Hi Robert > > Hey JB, > > > You are right. Reason of this « xml workaround » is that the service loader > > spec didn’t exist before OSGi r8. > > > > So now that Karaf 4.5 is OSGi r8 we can revisit some impl we did. > > Cool, I have filed https://issues.apache.org/jira/browse/KARAF-7768 to > track this. > > I'll try to circle back to it as I find some free cycles. > > Thanks, > Robert > > > > > Regards > > JB > > > > Le dim. 24 sept. 2023 à 22:41, Robert Varga a écrit : > > > >> Hello, > >> > >> now that we are going for Java 11, we need to deal with JPMS and the > >> migration is showing some friction I have not seen in OpenDaylight. > >> > >> OpenDaylight is a Karaf downstream, which requires Java 17 and is in a > >> shape I would expect it to Just Work(tm) sans Karaf. > >> > >> One of such points of friction is karaf.git/specs/java.xml -- which is > >> overriding JVM classes. > >> > >> As I understand it the point of this package override is to perform > >> resolution to OSGi registry in service of > >> https://issues.apache.org/jira/browse/KARAF-5680. > >> > >> If my understanding is correct, everything we are overriding here could > >> be just resolved via an OSGi-service loader. For example > >> XMLInputFactory.newInstance() says, among JVM-defaults, this: > >> > >> "Use the service-provider loading facility, defined by the ServiceLoader > >> class, to attempt to locate and load an implementation of the service > >> using the default loading mechanism: the service-provider loading > >> facility will use the current thread's context class loader to attempt > >> to load the service. If the context class loader is null, the system > >> class loader will be used." > >> > >> As I see it, we can satisfy the requirements of KARAF-5680 by saying the > >> Karaf container always implements Service Loader Mediator Specification > >> (https://docs.osgi.org/specification/osgi.cmpn/8.0.0/service.loader.html). > >> > >> In karaf.git terms, spifly is not a separate feature, but is always > >> included in Karaf. > >> > >> I mean, with JPMS, ServiceLoader is the platform-acknowledged extension > >> mechanism, hence we should be integrating no matter what... > >> > >> I this a sensible direction, or am I missing something? > >> > >> Regards, > >> Robert > >> > >
Re: jre.properties vs. JEP220?
It sounds good. Thanks ! Regards JB On Wed, Sep 27, 2023 at 6:35 PM Robert Varga wrote: > > On 27/09/2023 08.30, Jean-Baptiste Onofré wrote: > > Hi > > > > It makes sense to me (it’s something that I wanted to explore). > > So definitely worth to investigate. > > Cool. I think we can tuck this under > https://issues.apache.org/jira/browse/KARAF-7765, if you are okay with that. > > Regards, > Robert > > > > > Regards > > JB > > > > Le dim. 24 sept. 2023 à 21:45, Robert Varga a écrit : > > > >> Hello everyone, > >> > >> with karaf-4.5.0 requiring Java 11 > >> (https://issues.apache.org/jira/browse/KARAF-7754), there are a number > >> of places where we can safely forget about how JVM < 9 did things, which > >> could lead to simplifications. > >> > >> One of these is Karaf's jre.properties, which (as I understand it) > >> define the set of packages which are to be advertised by the OSGi > >> framework (bundle 0, or somesuch, sorry, I am quite rusty on the spec). > >> > >> JEP 220 (https://openjdk.org/jeps/220), integrated in Java 9, exposes > >> the set of runtime-available packages as jrt:/packages/ (see > >> https://bugs.openjdk.org/browse/JDK-8066492). > >> > >> This would mean we can figure out the set of packages at runtime, would > >> make jre.properties (and our adding a new jre-XY entry every 6 months), > >> superfluous. > >> > >> There is one wrinkle, which is javax.transaction.xa, but, with my all of > >> no knowledge of J2EE, I think this a problem we need to deal with only > >> until we transition to the jakarta namespaces (karaf-5?)[0] > >> > >> Does this effort sound reasonable, or am I missing something? > >> > >> Thanks, > >> Robert > >> > >> [0] I think it might make sense to list Karaf, and perhaps Pax Web, > >> somewhere searchable, like > >> https://jakarta.ee/blogs/javax-jakartaee-namespace-ecosystem-progress/ . > >> > >
Re: The meaning of karaf-bom
Hi Not really imho : each project does the way it considers the best. For instance, quarkus is using a bop approach similar to Karaf: it exposes all dependencies in the BOM as a guarantee about the versions working fine. The idea in Karaf bom is to clearly state the versions verified in Karaf. Users can always override the versions, but the BOM guarantees the qualified versions. Regards JB Le dim. 24 sept. 2023 à 22:54, Robert Varga a écrit : > Hello, > > One thing that strikes me is "Bill of Materials" as perceived by karaf-bom. > > As it currently stands, karaf-bom includes all declarations of > karaf.git/pom.xml. > > As I understand the bill-of-materials concept under Maven, it should > only list artifacts provided by a particular project, nothing more, > nothing less. > > In the latter regard, we should be only declaring org.apache.karaf > artifacts in karaf-bom. > > From a downstream's perspective, there is a difference between > importing karaf-bom (in which case the downstream takes the > resposibility to align any shared depdendencies) and karaf.git/pom.xml > (in which case I am trusting Karaf with a ton of dependencies). > > Currently, there is no distinction between those two. > > Is it fair to align karaf-bom with the above expectation (and hence not > leak things like org.slfj4.api's version)? > > As it stands there is no distinction, with this proposal current > downstreams wishing to retain current state would scope=import > karaf.git/pom.xml instead of karaf-bom (a change of maven coordinates) > with no otherwise-observable change. > > Does this make sense? > > Regards, > Robert >
Re: Questions about KARAF-5680
Hi Robert You are right. Reason of this « xml workaround » is that the service loader spec didn’t exist before OSGi r8. So now that Karaf 4.5 is OSGi r8 we can revisit some impl we did. Regards JB Le dim. 24 sept. 2023 à 22:41, Robert Varga a écrit : > Hello, > > now that we are going for Java 11, we need to deal with JPMS and the > migration is showing some friction I have not seen in OpenDaylight. > > OpenDaylight is a Karaf downstream, which requires Java 17 and is in a > shape I would expect it to Just Work(tm) sans Karaf. > > One of such points of friction is karaf.git/specs/java.xml -- which is > overriding JVM classes. > > As I understand it the point of this package override is to perform > resolution to OSGi registry in service of > https://issues.apache.org/jira/browse/KARAF-5680. > > If my understanding is correct, everything we are overriding here could > be just resolved via an OSGi-service loader. For example > XMLInputFactory.newInstance() says, among JVM-defaults, this: > > "Use the service-provider loading facility, defined by the ServiceLoader > class, to attempt to locate and load an implementation of the service > using the default loading mechanism: the service-provider loading > facility will use the current thread's context class loader to attempt > to load the service. If the context class loader is null, the system > class loader will be used." > > As I see it, we can satisfy the requirements of KARAF-5680 by saying the > Karaf container always implements Service Loader Mediator Specification > (https://docs.osgi.org/specification/osgi.cmpn/8.0.0/service.loader.html). > > In karaf.git terms, spifly is not a separate feature, but is always > included in Karaf. > > I mean, with JPMS, ServiceLoader is the platform-acknowledged extension > mechanism, hence we should be integrating no matter what... > > I this a sensible direction, or am I missing something? > > Regards, > Robert >
Re: jre.properties vs. JEP220?
Hi It makes sense to me (it’s something that I wanted to explore). So definitely worth to investigate. Regards JB Le dim. 24 sept. 2023 à 21:45, Robert Varga a écrit : > Hello everyone, > > with karaf-4.5.0 requiring Java 11 > (https://issues.apache.org/jira/browse/KARAF-7754), there are a number > of places where we can safely forget about how JVM < 9 did things, which > could lead to simplifications. > > One of these is Karaf's jre.properties, which (as I understand it) > define the set of packages which are to be advertised by the OSGi > framework (bundle 0, or somesuch, sorry, I am quite rusty on the spec). > > JEP 220 (https://openjdk.org/jeps/220), integrated in Java 9, exposes > the set of runtime-available packages as jrt:/packages/ (see > https://bugs.openjdk.org/browse/JDK-8066492). > > This would mean we can figure out the set of packages at runtime, would > make jre.properties (and our adding a new jre-XY entry every 6 months), > superfluous. > > There is one wrinkle, which is javax.transaction.xa, but, with my all of > no knowledge of J2EE, I think this a problem we need to deal with only > until we transition to the jakarta namespaces (karaf-5?)[0] > > Does this effort sound reasonable, or am I missing something? > > Thanks, > Robert > > [0] I think it might make sense to list Karaf, and perhaps Pax Web, > somewhere searchable, like > https://jakarta.ee/blogs/javax-jakartaee-namespace-ecosystem-progress/ . >
Re: [INFO] main branch has been updated to 4.5.0-SNAPSHOT
Hi Version aside, jakarta namespace support needs a more round of investigation, but specifically for Karaf, but more for dependencies used in Karaf: I'm thinking especially about OSGi Specs/R and Pax Web. So, I think it's a bit early to create Karaf 5.0.0. I would first start the best effort in Karaf 4.5.x with backward compatibility in mind (like having javax/jakarta features like for mail) and have clearly Jira created for breaking changes which would require 5.0.0 version shift. So, let's start on main/4.5.x and see what we see :) Regards JB On Thu, Sep 21, 2023 at 7:52 PM Matt Pavlovich wrote: > > Hi JB- > > For Jakarta-based Karaf, should we go ahead and call it Karaf 5.0.0? > > -Matt > > > On Sep 21, 2023, at 10:45 AM, Jean-Baptiste Onofré > > wrote: > > > > Hi guys, > > > > now that we released Karaf OSGi runtime 4.4.4 and 4.3.10: > > - I updated main branch to use 4.5.0-SNAPSHOT branch > > - I created karaf-4.4.x branch > > > > As a reminder, karaf-4.3.x will move "not active" when the first 4.5.0 > > version will be released. > > > > Regards > > JB >
[INFO] main branch has been updated to 4.5.0-SNAPSHOT
Hi guys, now that we released Karaf OSGi runtime 4.4.4 and 4.3.10: - I updated main branch to use 4.5.0-SNAPSHOT branch - I created karaf-4.4.x branch As a reminder, karaf-4.3.x will move "not active" when the first 4.5.0 version will be released. Regards JB
[ANN] Apache Karaf OSGi runtime 4.3.10 has been released!
The Karaf team is pleased to announce Apache Karaf OSGi runtime 4.3.10 release. This is a maintenance release, bringing fixes, new features and dependency updates: - fix race condition between the FeaturesService and FeatureDeploymentListener - fix --patch-module on Instance startup - add exec:groovy shell command - dependency updates including CVE fixes (Johnzon, BouncyCastle, Commons FileUpload, ...) - and much more! You can take a look on the Release Notes for details: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12352694 You can download this release here: https://karaf.apache.org/download.html Enjoy! The Apache Karaf team
[RESULT][VOTE] Apache Karaf OSGi runtime 4.3.10 release
Hi all, this vote passed with the following result: +1 (binding): Grzegorz Grzybek, François Papon, JB Onofré, Jamie Goodyear +1 (non binding): Serge Huber, Matt Pavlovich I'm promoting the artifacts on Maven Central and dist.apache.org. Then, I will update Jira, website and reporter. Then I will upload the Docker images and do the official announcement. Thanks all for your vote! Regards JB On Thu, Sep 14, 2023 at 6:33 PM Jean-Baptiste Onofré wrote: > > Hi guys, > > I submit Apache Karaf OSGi runtime 4.3.10 release to your vote. > > This release is a maintenance release bringing fixes and dependency updates. > Especially this release includes: > - fix race condition between the FeaturesService and FeatureDeploymentListener > - fix --patch-module on Instance startup > - add exec:groovy shell command > - dependency updates including CVE fixes (Johnzon, BouncyCastle, > Commons FileUpload) > > You can take a look on the Release Notes for details: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12352694 > > Maven Staging Repository: > https://repository.apache.org/content/repositories/orgapachekaraf-1188/ > > Dist Staging Repository: > https://dist.apache.org/repos/dist/dev/karaf/4.3.10/ > > Git tag: > karaf-4.3.10 > > Please vote to approve this release: > [ ] +1 Approve the release > [ ] -1 Don't approve the release (please provide specific comments) > > This vote will be open for at least 72 hours. > > Regards > JB
[ANN] Apache Karaf OSGi runtime 4.4.4 has been released!
The Karaf team is pleased to announce Apache Karaf OSGi runtime 4.4.4 release. This is a a maintenance release, bringing a lot of dependency updates and fixes, especially: - fix race condition between the FeatureService and FeatureDeploymentListener - fix --patch-module on Instance startup - add exec:groovy shell command - a lot of dependency updated including CVE fixes (Johnzon, BouncyCastle, Commons FileUpload, and much more !) - better JDK20+ support - and much more! You can take a look on the Release Notes for details: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12352693 You can download this release here: https://karaf.apache.org/download.html Enjoy ! The Apache Karaf team
[RESULT][VOTE] Apache Karaf OSGi runtime 4.4.4 release
Hi all, this vote passed with the following result: +1 (binding): Grzegorz Grzybek, JB Onofré, François Papon, Jamie Goodyear +1 (non binding): Robert Varga, Jakub Herkel, Romain Manni-Bucau, Serge Huber, Matt Pavlovich, Steinar Bang I'm promoting the artifacts on Maven Central and dist.apache.org, I will update Jira, website and reporter, I will upload Docker images, then I will do the official announcement. Thanks all for your vote ! NB: I'm gonna create the karaf-4.4.x branch and I will update main to 4.5.x version. Regards JB On Tue, Sep 12, 2023 at 5:06 PM Jean-Baptiste Onofré wrote: > > Hi guys, > > After long weeks of wait, I submit Apache Karaf OSGi runtime 4.4.4 > release to your vote. > > This release is a maintenance release bringing fixes and dependency updates. > Especially this release includes: > - fix race condition between the FeaturesService and FeatureDeploymentListener > - fix --patch-module on Instance startup > - add exec:groovy shell command > - dependency updates including CVE fixes (Johnzon, BouncyCastle, > Commons FileUpload) > - better JDK20 support > > You can take a look on the Release Notes for details: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12352693 > > Maven Staging Repository: > https://repository.apache.org/content/repositories/orgapachekaraf-1186/ > > Dist Staging Repository: > https://dist.apache.org/repos/dist/dev/karaf/4.4.4/ > > Git tag: > karaf-4.4.4 > > Please vote to approve this release: > [ ] +1 Approve the release > [ ] -1 Don't approve the release (please provide specific comments) > > This vote will be open for at least 72 hours. > > Regards > JB
Re: [VOTE] Apache Karaf OSGi runtime 4.3.10 release
+1 (binding) Regards JB On Thu, Sep 14, 2023 at 6:33 PM Jean-Baptiste Onofré wrote: > > Hi guys, > > I submit Apache Karaf OSGi runtime 4.3.10 release to your vote. > > This release is a maintenance release bringing fixes and dependency updates. > Especially this release includes: > - fix race condition between the FeaturesService and FeatureDeploymentListener > - fix --patch-module on Instance startup > - add exec:groovy shell command > - dependency updates including CVE fixes (Johnzon, BouncyCastle, > Commons FileUpload) > > You can take a look on the Release Notes for details: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12352694 > > Maven Staging Repository: > https://repository.apache.org/content/repositories/orgapachekaraf-1188/ > > Dist Staging Repository: > https://dist.apache.org/repos/dist/dev/karaf/4.3.10/ > > Git tag: > karaf-4.3.10 > > Please vote to approve this release: > [ ] +1 Approve the release > [ ] -1 Don't approve the release (please provide specific comments) > > This vote will be open for at least 72 hours. > > Regards > JB
[VOTE] Apache Karaf OSGi runtime 4.3.10 release
Hi guys, I submit Apache Karaf OSGi runtime 4.3.10 release to your vote. This release is a maintenance release bringing fixes and dependency updates. Especially this release includes: - fix race condition between the FeaturesService and FeatureDeploymentListener - fix --patch-module on Instance startup - add exec:groovy shell command - dependency updates including CVE fixes (Johnzon, BouncyCastle, Commons FileUpload) You can take a look on the Release Notes for details: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12352694 Maven Staging Repository: https://repository.apache.org/content/repositories/orgapachekaraf-1188/ Dist Staging Repository: https://dist.apache.org/repos/dist/dev/karaf/4.3.10/ Git tag: karaf-4.3.10 Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Don't approve the release (please provide specific comments) This vote will be open for at least 72 hours. Regards JB
Re: [VOTE] Apache Karaf OSGi runtime 4.4.4 release
+1 (binding) Regards JB On Tue, Sep 12, 2023 at 5:06 PM Jean-Baptiste Onofré wrote: > > Hi guys, > > After long weeks of wait, I submit Apache Karaf OSGi runtime 4.4.4 > release to your vote. > > This release is a maintenance release bringing fixes and dependency updates. > Especially this release includes: > - fix race condition between the FeaturesService and FeatureDeploymentListener > - fix --patch-module on Instance startup > - add exec:groovy shell command > - dependency updates including CVE fixes (Johnzon, BouncyCastle, > Commons FileUpload) > - better JDK20 support > > You can take a look on the Release Notes for details: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12352693 > > Maven Staging Repository: > https://repository.apache.org/content/repositories/orgapachekaraf-1186/ > > Dist Staging Repository: > https://dist.apache.org/repos/dist/dev/karaf/4.4.4/ > > Git tag: > karaf-4.4.4 > > Please vote to approve this release: > [ ] +1 Approve the release > [ ] -1 Don't approve the release (please provide specific comments) > > This vote will be open for at least 72 hours. > > Regards > JB
Re: [VOTE] Apache Karaf OSGi runtime 4.4.4 release
Hi Robert, About jline, it has been postponed because it breaks the tab binding in the shell console, so I need more time to fix that (see https://issues.apache.org/jira/browse/KARAF-7723). commons-compress has been upgraded with the version available at time of release preparation (https://issues.apache.org/jira/browse/KARAF-7702). I will update for next release. wagon needs also pax-url update (in progress). NB: Karaf 4.4.5 will be submitted to vote very soon as I would like to provide Spring 6 features. Regards JB On Tue, Sep 12, 2023 at 9:14 PM Robert Varga wrote: > > On 12/09/2023 17.06, Jean-Baptiste Onofré wrote: > > Hi guys, > > Hey JB, > > > After long weeks of wait, I submit Apache Karaf OSGi runtime 4.4.4 > > release to your vote. > > Thanks a lot! > > > This release is a maintenance release bringing fixes and dependency updates. > > Especially this release includes: > > - fix race condition between the FeaturesService and > > FeatureDeploymentListener > > - fix --patch-module on Instance startup > > - add exec:groovy shell command > > - dependency updates including CVE fixes (Johnzon, BouncyCastle, > > Commons FileUpload) > > - better JDK20 support > > So there are a few third party upgrades missing: > - wagon-1.5.3 > - jline-3.23.0 > - commons-compress-1.24.0 > > but I do not believe they are worth a respin. I have this upgrade > passing basic upgrade tests in ODL. > > > Please vote to approve this release: > > [ ] +1 Approve the release > > [ ] -1 Don't approve the release (please provide specific comments) > > +1, non-binding. > > Thanks again, > Robert
[VOTE] Apache Karaf OSGi runtime 4.4.4 release
Hi guys, After long weeks of wait, I submit Apache Karaf OSGi runtime 4.4.4 release to your vote. This release is a maintenance release bringing fixes and dependency updates. Especially this release includes: - fix race condition between the FeaturesService and FeatureDeploymentListener - fix --patch-module on Instance startup - add exec:groovy shell command - dependency updates including CVE fixes (Johnzon, BouncyCastle, Commons FileUpload) - better JDK20 support You can take a look on the Release Notes for details: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12352693 Maven Staging Repository: https://repository.apache.org/content/repositories/orgapachekaraf-1186/ Dist Staging Repository: https://dist.apache.org/repos/dist/dev/karaf/4.4.4/ Git tag: karaf-4.4.4 Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Don't approve the release (please provide specific comments) This vote will be open for at least 72 hours. Regards JB
September 2023 board report
Hi all, I prepared the board report for September: https://cwiki.apache.org/confluence/display/KARAF/Board+Reports It's pretty short as the activity was pretty low during summer break. We are now back to regular pace and fully committed to submit releases to vote asap. Let me know if you want to add something on the board report, I would like to submit the report asap. Thanks ! Regards JB
Re: Towards releases
Hi guys We are almost good for releases. As I took way too much time for these releases (and sorry about that), I will submit 4.3/4.4 releases to vote during the week end, postponing few changes for next releases. We will be back to the release pace of at least a release per quarter. On the other hand, as soon as these releases are out, I will move forward on Karaf 4.5.x next week. Sorry for the long process for these releases, we are now back on our regular pace. Regards JB On Mon, Aug 21, 2023 at 7:36 AM Jean-Baptiste Onofré wrote: > > Hi guys > > I'm back from vacation. I'm resuming the releases preparation, the > vote emails should come soon. Stay tuned ! > > Regards > JB > > On Wed, Jul 26, 2023 at 3:34 PM Grzegorz Grzybek wrote: > > > > Hello > > > > Pax Logging 1.12.6 + 2.2.3, Pax Transx 0.5.4, Pax JMS 1.1.3 and Pax JDBC > > 1.5.6 are already in Maven Central. > > > > I'm just running integration tests on Pax Web 8.0.21 and 9.0.10 and these > > releases should be in Maven Central in <1 hour. > > > > Thanks for the patience and sorry for delay! > > > > regards > > Grzegorz Grzybek > > > > wt., 25 lip 2023 o 07:52 Jean-Baptiste Onofré > > napisał(a): > >> > >> OK great. I will update in Karaf (we can wait one more day for the > >> release, no problem at all). > >> > >> Regards > >> JB > >> > >> On Tue, Jul 25, 2023 at 7:40 AM Grzegorz Grzybek > >> wrote: > >> > > >> > Hello > >> > > >> > From Pax side, there are two driver updates in Pax JDBC and one issue I > >> > want to investigate for Pax JMS. > >> > If I can't do it today (hoping to have releases for next Karaf), I'll > >> > let you know to now wait ;) > >> > > >> > For Pax Web, I also have 8.0.21 waiting with Undertow and Tomcat > >> > upgrades so I can prepare the releases today. > >> > > >> > regards > >> > Grzegorz Grzybek > >> > > >> > wt., 25 lip 2023 o 06:59 Jean-Baptiste Onofré > >> > napisał(a): > >> >> > >> >> Hi, > >> >> > >> >> The release preparation is almost done. I'm just doing a triage on > >> >> Jira and I will cut the release and I will send the vote email. > >> >> > >> >> Stay tuned! > >> >> > >> >> Regards > >> >> JB > >> >> > >> >> On Fri, Jul 21, 2023 at 6:36 AM Jean-Baptiste Onofré > >> >> wrote: > >> >> > > >> >> > Hi guys, > >> >> > > >> >> > I know I'm super late about these releases :/ > >> >> > > >> >> > The Karaf releases (especially 4.4.4) will be in vote next week (I > >> >> > merged the final touches during the weekend). > >> >> > > >> >> > Regards > >> >> > JB > >> >> > > >> >> > On Thu, Jun 15, 2023 at 5:08 PM Jean-Baptiste Onofré > >> >> > wrote: > >> >> > > > >> >> > > Hi guys, > >> >> > > > >> >> > > even if I'm a bit late on the original releases schedule, it's > >> >> > > almost there :) > >> >> > > > >> >> > > So stay tuned, the votes will start soon. > >> >> > > > >> >> > > Regards > >> >> > > JB > >> >> > > > >> >> > > On Mon, May 29, 2023 at 7:45 AM Jean-Baptiste Onofré > >> >> > > wrote: > >> >> > > > > >> >> > > > Hi guys, > >> >> > > > > >> >> > > > I'm doing the final touches on releases preparation. We should be > >> >> > > > good > >> >> > > > for a vote this week. > >> >> > > > > >> >> > > > I will keep you posted. > >> >> > > > > >> >> > > > Regards > >> >> > > > JB > >> >> > > > > >> >> > > > On Mon, May 22, 2023 at 9:22 AM Jean-Baptiste Onofré > >> >> > > > wrote: > >> >> > > > > > >> >> > > > > Hi guys, &
Re: Towards releases
Hi guys I'm back from vacation. I'm resuming the releases preparation, the vote emails should come soon. Stay tuned ! Regards JB On Wed, Jul 26, 2023 at 3:34 PM Grzegorz Grzybek wrote: > > Hello > > Pax Logging 1.12.6 + 2.2.3, Pax Transx 0.5.4, Pax JMS 1.1.3 and Pax JDBC > 1.5.6 are already in Maven Central. > > I'm just running integration tests on Pax Web 8.0.21 and 9.0.10 and these > releases should be in Maven Central in <1 hour. > > Thanks for the patience and sorry for delay! > > regards > Grzegorz Grzybek > > wt., 25 lip 2023 o 07:52 Jean-Baptiste Onofré napisał(a): >> >> OK great. I will update in Karaf (we can wait one more day for the >> release, no problem at all). >> >> Regards >> JB >> >> On Tue, Jul 25, 2023 at 7:40 AM Grzegorz Grzybek >> wrote: >> > >> > Hello >> > >> > From Pax side, there are two driver updates in Pax JDBC and one issue I >> > want to investigate for Pax JMS. >> > If I can't do it today (hoping to have releases for next Karaf), I'll let >> > you know to now wait ;) >> > >> > For Pax Web, I also have 8.0.21 waiting with Undertow and Tomcat upgrades >> > so I can prepare the releases today. >> > >> > regards >> > Grzegorz Grzybek >> > >> > wt., 25 lip 2023 o 06:59 Jean-Baptiste Onofré >> > napisał(a): >> >> >> >> Hi, >> >> >> >> The release preparation is almost done. I'm just doing a triage on >> >> Jira and I will cut the release and I will send the vote email. >> >> >> >> Stay tuned! >> >> >> >> Regards >> >> JB >> >> >> >> On Fri, Jul 21, 2023 at 6:36 AM Jean-Baptiste Onofré >> >> wrote: >> >> > >> >> > Hi guys, >> >> > >> >> > I know I'm super late about these releases :/ >> >> > >> >> > The Karaf releases (especially 4.4.4) will be in vote next week (I >> >> > merged the final touches during the weekend). >> >> > >> >> > Regards >> >> > JB >> >> > >> >> > On Thu, Jun 15, 2023 at 5:08 PM Jean-Baptiste Onofré >> >> > wrote: >> >> > > >> >> > > Hi guys, >> >> > > >> >> > > even if I'm a bit late on the original releases schedule, it's almost >> >> > > there :) >> >> > > >> >> > > So stay tuned, the votes will start soon. >> >> > > >> >> > > Regards >> >> > > JB >> >> > > >> >> > > On Mon, May 29, 2023 at 7:45 AM Jean-Baptiste Onofré >> >> > > wrote: >> >> > > > >> >> > > > Hi guys, >> >> > > > >> >> > > > I'm doing the final touches on releases preparation. We should be >> >> > > > good >> >> > > > for a vote this week. >> >> > > > >> >> > > > I will keep you posted. >> >> > > > >> >> > > > Regards >> >> > > > JB >> >> > > > >> >> > > > On Mon, May 22, 2023 at 9:22 AM Jean-Baptiste Onofré >> >> > > > wrote: >> >> > > > > >> >> > > > > Hi guys, >> >> > > > > >> >> > > > > I made good progress on releases preparation. I will create a >> >> > > > > bunch of >> >> > > > > PR soon (starting from today). >> >> > > > > >> >> > > > > I should be able to submit releases to vote by the end of the >> >> > > > > week. >> >> > > > > >> >> > > > > I will keep you posted. >> >> > > > > >> >> > > > > Regards >> >> > > > > JB >> >> > > > > >> >> > > > > On Thu, May 4, 2023 at 4:57 PM Jean-Baptiste Onofré >> >> > > > > wrote: >> >> > > > > > >> >> > > > > > Sorry guys, I'm late on the release pace. I'm now working on >> >> > > > > > releases >> >> > > > > > preparation, starting from Karaf runtime. >> >> > > > > > >> >> > > > > > I should be able to submit a first batch of releases by the end >> >> > > > > > of this week. >> >> > > > > > >> >> > > > > > Regards >> >> > > > > > JB >> >> > > > > > >> >> > > > > > On Thu, Jan 26, 2023 at 8:31 AM Jean-Baptiste Onofré >> >> > > > > > wrote: >> >> > > > > > > >> >> > > > > > > Hi guys, >> >> > > > > > > >> >> > > > > > > FYI, I'm almost done to prepare new Decanter and Cellar >> >> > > > > > > releases. >> >> > > > > > > >> >> > > > > > > I will move forward with the votes during the weekend. >> >> > > > > > > >> >> > > > > > > After these releases, I propose to move forward on the >> >> > > > > > > subprojects >> >> > > > > > > cleanup (cave, ...) as we discussed on the mailing list. >> >> > > > > > > >> >> > > > > > > I will keep you posted. >> >> > > > > > > >> >> > > > > > > Regards >> >> > > > > > > JB
Re: Towards releases
OK great. I will update in Karaf (we can wait one more day for the release, no problem at all). Regards JB On Tue, Jul 25, 2023 at 7:40 AM Grzegorz Grzybek wrote: > > Hello > > From Pax side, there are two driver updates in Pax JDBC and one issue I want > to investigate for Pax JMS. > If I can't do it today (hoping to have releases for next Karaf), I'll let you > know to now wait ;) > > For Pax Web, I also have 8.0.21 waiting with Undertow and Tomcat upgrades so > I can prepare the releases today. > > regards > Grzegorz Grzybek > > wt., 25 lip 2023 o 06:59 Jean-Baptiste Onofré napisał(a): >> >> Hi, >> >> The release preparation is almost done. I'm just doing a triage on >> Jira and I will cut the release and I will send the vote email. >> >> Stay tuned! >> >> Regards >> JB >> >> On Fri, Jul 21, 2023 at 6:36 AM Jean-Baptiste Onofré >> wrote: >> > >> > Hi guys, >> > >> > I know I'm super late about these releases :/ >> > >> > The Karaf releases (especially 4.4.4) will be in vote next week (I >> > merged the final touches during the weekend). >> > >> > Regards >> > JB >> > >> > On Thu, Jun 15, 2023 at 5:08 PM Jean-Baptiste Onofré >> > wrote: >> > > >> > > Hi guys, >> > > >> > > even if I'm a bit late on the original releases schedule, it's almost >> > > there :) >> > > >> > > So stay tuned, the votes will start soon. >> > > >> > > Regards >> > > JB >> > > >> > > On Mon, May 29, 2023 at 7:45 AM Jean-Baptiste Onofré >> > > wrote: >> > > > >> > > > Hi guys, >> > > > >> > > > I'm doing the final touches on releases preparation. We should be good >> > > > for a vote this week. >> > > > >> > > > I will keep you posted. >> > > > >> > > > Regards >> > > > JB >> > > > >> > > > On Mon, May 22, 2023 at 9:22 AM Jean-Baptiste Onofré >> > > > wrote: >> > > > > >> > > > > Hi guys, >> > > > > >> > > > > I made good progress on releases preparation. I will create a bunch >> > > > > of >> > > > > PR soon (starting from today). >> > > > > >> > > > > I should be able to submit releases to vote by the end of the week. >> > > > > >> > > > > I will keep you posted. >> > > > > >> > > > > Regards >> > > > > JB >> > > > > >> > > > > On Thu, May 4, 2023 at 4:57 PM Jean-Baptiste Onofré >> > > > > wrote: >> > > > > > >> > > > > > Sorry guys, I'm late on the release pace. I'm now working on >> > > > > > releases >> > > > > > preparation, starting from Karaf runtime. >> > > > > > >> > > > > > I should be able to submit a first batch of releases by the end of >> > > > > > this week. >> > > > > > >> > > > > > Regards >> > > > > > JB >> > > > > > >> > > > > > On Thu, Jan 26, 2023 at 8:31 AM Jean-Baptiste Onofré >> > > > > > wrote: >> > > > > > > >> > > > > > > Hi guys, >> > > > > > > >> > > > > > > FYI, I'm almost done to prepare new Decanter and Cellar releases. >> > > > > > > >> > > > > > > I will move forward with the votes during the weekend. >> > > > > > > >> > > > > > > After these releases, I propose to move forward on the >> > > > > > > subprojects >> > > > > > > cleanup (cave, ...) as we discussed on the mailing list. >> > > > > > > >> > > > > > > I will keep you posted. >> > > > > > > >> > > > > > > Regards >> > > > > > > JB
Re: Towards releases
Hi, The release preparation is almost done. I'm just doing a triage on Jira and I will cut the release and I will send the vote email. Stay tuned! Regards JB On Fri, Jul 21, 2023 at 6:36 AM Jean-Baptiste Onofré wrote: > > Hi guys, > > I know I'm super late about these releases :/ > > The Karaf releases (especially 4.4.4) will be in vote next week (I > merged the final touches during the weekend). > > Regards > JB > > On Thu, Jun 15, 2023 at 5:08 PM Jean-Baptiste Onofré > wrote: > > > > Hi guys, > > > > even if I'm a bit late on the original releases schedule, it's almost there > > :) > > > > So stay tuned, the votes will start soon. > > > > Regards > > JB > > > > On Mon, May 29, 2023 at 7:45 AM Jean-Baptiste Onofré > > wrote: > > > > > > Hi guys, > > > > > > I'm doing the final touches on releases preparation. We should be good > > > for a vote this week. > > > > > > I will keep you posted. > > > > > > Regards > > > JB > > > > > > On Mon, May 22, 2023 at 9:22 AM Jean-Baptiste Onofré > > > wrote: > > > > > > > > Hi guys, > > > > > > > > I made good progress on releases preparation. I will create a bunch of > > > > PR soon (starting from today). > > > > > > > > I should be able to submit releases to vote by the end of the week. > > > > > > > > I will keep you posted. > > > > > > > > Regards > > > > JB > > > > > > > > On Thu, May 4, 2023 at 4:57 PM Jean-Baptiste Onofré > > > > wrote: > > > > > > > > > > Sorry guys, I'm late on the release pace. I'm now working on releases > > > > > preparation, starting from Karaf runtime. > > > > > > > > > > I should be able to submit a first batch of releases by the end of > > > > > this week. > > > > > > > > > > Regards > > > > > JB > > > > > > > > > > On Thu, Jan 26, 2023 at 8:31 AM Jean-Baptiste Onofré > > > > > wrote: > > > > > > > > > > > > Hi guys, > > > > > > > > > > > > FYI, I'm almost done to prepare new Decanter and Cellar releases. > > > > > > > > > > > > I will move forward with the votes during the weekend. > > > > > > > > > > > > After these releases, I propose to move forward on the subprojects > > > > > > cleanup (cave, ...) as we discussed on the mailing list. > > > > > > > > > > > > I will keep you posted. > > > > > > > > > > > > Regards > > > > > > JB
Re: karaf-4.5.x?
As it works fine, I plan to upgrade to Pax Logging 2.2.2 for Karaf 4.4.4. No need to wait for 4.5.x. Regards JB On Fri, Jul 21, 2023 at 7:59 AM Grzegorz Grzybek wrote: > > Hello > > For 2.2.x, Pax Logging 2.2.1 was the version where SLF4J 2.0 packages are > exported (see: #504 > <https://github.com/ops4j/org.ops4j.pax.logging/issues/504>[1]). > > Mind that the API for SLF4J didn't really change and the "big" thing is > different discovery of logging implementation (that's why outside of OSGi, > SLF4J 2.0 has to be combined with Logback 1.3+ or dedicated > log4j-slf4j2-impl). It doesn't really impact Pax Logging users. > > regards > Grzegorz Grzybek > === > [1]: https://github.com/ops4j/org.ops4j.pax.logging/issues/504 > > pt., 21 lip 2023 o 06:35 Jean-Baptiste Onofré napisał(a): > > > Hi > > > > I'm working on Karaf releases and plan to create 4.5.x after 4.4.4, > > I'm a bit late in the preparation but the releases votes are planned > > for next week. > > > > However, regarding slf4j 2, Pax Logging already exports the packages > > so I have to check the Pax Logging versions used in Karaf. > > > > Regards > > JB > > > > On Thu, Jul 20, 2023 at 7:54 PM Łukasz Dywicki > > wrote: > > > > > > I am reactivating this thread because I just ran into issue with > > > dependency which pulls slf4j 2.0.x API. > > > Given it is already 6 months since last message in this topic, is it > > > right time to start 4.5.x branch? > > > > > > Cheers, > > > Łukasz > > > > > > On 13.01.2023 07:23, Jean-Baptiste Onofré wrote: > > > > Hi Robert, > > > > > > > > It makes sense. I will prepare 4.5.x on Jira and I will create the > > > > 4.4.x branch and move main on the 4.5.x version. > > > > > > > > Let me first complete the 4.3.9 release and other Decanter/Cellar > > > > releases first. > > > > > > > > Thanks ! > > > > Regards > > > > JB > > > > > > > > On Thu, Jan 12, 2023 at 9:45 PM Robert Varga wrote: > > > >> > > > >> On 08/01/2023 08:33, Mark Derricutt wrote: > > > >>> On 8 Jan 2023, at 20:14, Jean-Baptiste Onofré wrote: > > > >>> > > > >>>> Java 11 is not a point as it's already used on Karaf 4.4.x. > > > >>> > > > >>> Altho it seems we can run Karaf 4.4.x under JDK 8 - so now I'm > > curious. > > > >>> I assume nothings being targeting JDK 9+ byte code then. > > > >> > > > >> Right, the karaf-4.4 contract is "YMMV". My proposal here is to switch > > > >> to "./bin/karaf will refuse to run unless you have a JAVA_HOME that > > > >> points to Java 11+". > > > >> > > > >> Regards, > > > >> Robert > >
Re: Towards releases
Hi guys, I know I'm super late about these releases :/ The Karaf releases (especially 4.4.4) will be in vote next week (I merged the final touches during the weekend). Regards JB On Thu, Jun 15, 2023 at 5:08 PM Jean-Baptiste Onofré wrote: > > Hi guys, > > even if I'm a bit late on the original releases schedule, it's almost there :) > > So stay tuned, the votes will start soon. > > Regards > JB > > On Mon, May 29, 2023 at 7:45 AM Jean-Baptiste Onofré > wrote: > > > > Hi guys, > > > > I'm doing the final touches on releases preparation. We should be good > > for a vote this week. > > > > I will keep you posted. > > > > Regards > > JB > > > > On Mon, May 22, 2023 at 9:22 AM Jean-Baptiste Onofré > > wrote: > > > > > > Hi guys, > > > > > > I made good progress on releases preparation. I will create a bunch of > > > PR soon (starting from today). > > > > > > I should be able to submit releases to vote by the end of the week. > > > > > > I will keep you posted. > > > > > > Regards > > > JB > > > > > > On Thu, May 4, 2023 at 4:57 PM Jean-Baptiste Onofré > > > wrote: > > > > > > > > Sorry guys, I'm late on the release pace. I'm now working on releases > > > > preparation, starting from Karaf runtime. > > > > > > > > I should be able to submit a first batch of releases by the end of this > > > > week. > > > > > > > > Regards > > > > JB > > > > > > > > On Thu, Jan 26, 2023 at 8:31 AM Jean-Baptiste Onofré > > > > wrote: > > > > > > > > > > Hi guys, > > > > > > > > > > FYI, I'm almost done to prepare new Decanter and Cellar releases. > > > > > > > > > > I will move forward with the votes during the weekend. > > > > > > > > > > After these releases, I propose to move forward on the subprojects > > > > > cleanup (cave, ...) as we discussed on the mailing list. > > > > > > > > > > I will keep you posted. > > > > > > > > > > Regards > > > > > JB
Re: karaf-4.5.x?
Hi I'm working on Karaf releases and plan to create 4.5.x after 4.4.4, I'm a bit late in the preparation but the releases votes are planned for next week. However, regarding slf4j 2, Pax Logging already exports the packages so I have to check the Pax Logging versions used in Karaf. Regards JB On Thu, Jul 20, 2023 at 7:54 PM Łukasz Dywicki wrote: > > I am reactivating this thread because I just ran into issue with > dependency which pulls slf4j 2.0.x API. > Given it is already 6 months since last message in this topic, is it > right time to start 4.5.x branch? > > Cheers, > Łukasz > > On 13.01.2023 07:23, Jean-Baptiste Onofré wrote: > > Hi Robert, > > > > It makes sense. I will prepare 4.5.x on Jira and I will create the > > 4.4.x branch and move main on the 4.5.x version. > > > > Let me first complete the 4.3.9 release and other Decanter/Cellar > > releases first. > > > > Thanks ! > > Regards > > JB > > > > On Thu, Jan 12, 2023 at 9:45 PM Robert Varga wrote: > >> > >> On 08/01/2023 08:33, Mark Derricutt wrote: > >>> On 8 Jan 2023, at 20:14, Jean-Baptiste Onofré wrote: > >>> > >>>> Java 11 is not a point as it's already used on Karaf 4.4.x. > >>> > >>> Altho it seems we can run Karaf 4.4.x under JDK 8 - so now I'm curious. > >>> I assume nothings being targeting JDK 9+ byte code then. > >> > >> Right, the karaf-4.4 contract is "YMMV". My proposal here is to switch > >> to "./bin/karaf will refuse to run unless you have a JAVA_HOME that > >> points to Java 11+". > >> > >> Regards, > >> Robert
Re: Towards releases
Hi guys, even if I'm a bit late on the original releases schedule, it's almost there :) So stay tuned, the votes will start soon. Regards JB On Mon, May 29, 2023 at 7:45 AM Jean-Baptiste Onofré wrote: > > Hi guys, > > I'm doing the final touches on releases preparation. We should be good > for a vote this week. > > I will keep you posted. > > Regards > JB > > On Mon, May 22, 2023 at 9:22 AM Jean-Baptiste Onofré > wrote: > > > > Hi guys, > > > > I made good progress on releases preparation. I will create a bunch of > > PR soon (starting from today). > > > > I should be able to submit releases to vote by the end of the week. > > > > I will keep you posted. > > > > Regards > > JB > > > > On Thu, May 4, 2023 at 4:57 PM Jean-Baptiste Onofré > > wrote: > > > > > > Sorry guys, I'm late on the release pace. I'm now working on releases > > > preparation, starting from Karaf runtime. > > > > > > I should be able to submit a first batch of releases by the end of this > > > week. > > > > > > Regards > > > JB > > > > > > On Thu, Jan 26, 2023 at 8:31 AM Jean-Baptiste Onofré > > > wrote: > > > > > > > > Hi guys, > > > > > > > > FYI, I'm almost done to prepare new Decanter and Cellar releases. > > > > > > > > I will move forward with the votes during the weekend. > > > > > > > > After these releases, I propose to move forward on the subprojects > > > > cleanup (cave, ...) as we discussed on the mailing list. > > > > > > > > I will keep you posted. > > > > > > > > Regards > > > > JB
Re: Board Report for June 2023
The report has been submitted to the board. Thanks all ! Regards JB On Wed, Jun 7, 2023 at 5:54 PM Grzegorz Grzybek wrote: > > +1 > > regards > Grzegorz Grzybek > > śr., 7 cze 2023 o 17:13 Francois Papon > napisał(a): > > > Look good to me! > > > > Thanks JB! > > > > regards, > > > > On 06/06/2023 10:53, Jean-Baptiste Onofré wrote: > > > Hi guys, > > > > > > I prepared the board report for this month: > > > > > > https://cwiki.apache.org/confluence/display/KARAF/Board+Reports > > > > > > Please take a look and update if needed. I would like to send the report > > asap. > > > > > > Thanks ! > > > Regards > > > JB > >
Re: Board Report for June 2023
If no objection, I will send the report tonight my time. Regards JB On Tue, Jun 6, 2023 at 10:53 AM Jean-Baptiste Onofré wrote: > > Hi guys, > > I prepared the board report for this month: > > https://cwiki.apache.org/confluence/display/KARAF/Board+Reports > > Please take a look and update if needed. I would like to send the report asap. > > Thanks ! > Regards > JB
Re: question about @Reference and @Component
Hi Nick,
Please use the users mailing list for this kind of question (dev
mailing list is more for discussions between Karaf developers).
FYI,, I think I already replied to you as private message :)
Regards
JB
On Tue, Jun 6, 2023 at 3:31 PM z8...@yahoo.com.ar.INVALID
wrote:
>
> I'm trying to understand how those annotations work.I have the following
> Activator.class and MyConf.class in the same bundle.
> The Activator code:
> @Component@Slf4jpublic class Activator implements BundleActivator,
> ManagedService {
> private static Logger logger =
> LoggerFactory.getLogger(Activator.class);private static final String
> CONFIG_PID = "mytest";private ServiceRegistration serviceReg;
> @Referenceprivate MyConf conf;public void start(BundleContext context) {
> Hashtable properties = new Hashtable Object>();properties.put(Constants.SERVICE_PID, CONFIG_PID);serviceReg =
> context.registerService(ManagedService.class.getName(), this , properties); }
>public void stop(BundleContext context) {serviceReg.unregister();}
> @SuppressWarnings("rawtypes")@Overridepublic void
> updated(Dictionary config) throws ConfigurationException {if (config == null)
> {return;}conf.setFoo((String) config.get("foo"));conf.refresh();}
>
> and MyConf:
> @Componentpublic class MyConf {private String foo = "bar";public MyConf()
> {}public String getFoo() {return foo;}
> public void setFoo(String foo) {this.foo = foo;}public void refresh()
> {System.out.println("foo=" + this.foo);}
> }
> It seems pretty basic, but when I deploy it in Karaf says:
> Status: WaitingDeclarative
> Servicesar.com.aerolineas.esb.operaciones.pruebas.Activator (21) missing
> references: conf
> and in the log, there's a NullPointerException at conf.setFoo in the
> Activator, as if the framework never instantiate + inject MyConf. Am I
> missing something?
> Thanks in advaced.Nick.
>
Board Report for June 2023
Hi guys, I prepared the board report for this month: https://cwiki.apache.org/confluence/display/KARAF/Board+Reports Please take a look and update if needed. I would like to send the report asap. Thanks ! Regards JB
Re: Towards releases
Hi guys, I'm doing the final touches on releases preparation. We should be good for a vote this week. I will keep you posted. Regards JB On Mon, May 22, 2023 at 9:22 AM Jean-Baptiste Onofré wrote: > > Hi guys, > > I made good progress on releases preparation. I will create a bunch of > PR soon (starting from today). > > I should be able to submit releases to vote by the end of the week. > > I will keep you posted. > > Regards > JB > > On Thu, May 4, 2023 at 4:57 PM Jean-Baptiste Onofré wrote: > > > > Sorry guys, I'm late on the release pace. I'm now working on releases > > preparation, starting from Karaf runtime. > > > > I should be able to submit a first batch of releases by the end of this > > week. > > > > Regards > > JB > > > > On Thu, Jan 26, 2023 at 8:31 AM Jean-Baptiste Onofré > > wrote: > > > > > > Hi guys, > > > > > > FYI, I'm almost done to prepare new Decanter and Cellar releases. > > > > > > I will move forward with the votes during the weekend. > > > > > > After these releases, I propose to move forward on the subprojects > > > cleanup (cave, ...) as we discussed on the mailing list. > > > > > > I will keep you posted. > > > > > > Regards > > > JB
Re: Towards releases
Hi guys, I made good progress on releases preparation. I will create a bunch of PR soon (starting from today). I should be able to submit releases to vote by the end of the week. I will keep you posted. Regards JB On Thu, May 4, 2023 at 4:57 PM Jean-Baptiste Onofré wrote: > > Sorry guys, I'm late on the release pace. I'm now working on releases > preparation, starting from Karaf runtime. > > I should be able to submit a first batch of releases by the end of this week. > > Regards > JB > > On Thu, Jan 26, 2023 at 8:31 AM Jean-Baptiste Onofré > wrote: > > > > Hi guys, > > > > FYI, I'm almost done to prepare new Decanter and Cellar releases. > > > > I will move forward with the votes during the weekend. > > > > After these releases, I propose to move forward on the subprojects > > cleanup (cave, ...) as we discussed on the mailing list. > > > > I will keep you posted. > > > > Regards > > JB
Re: Towards releases
Sorry guys, I'm late on the release pace. I'm now working on releases preparation, starting from Karaf runtime. I should be able to submit a first batch of releases by the end of this week. Regards JB On Thu, Jan 26, 2023 at 8:31 AM Jean-Baptiste Onofré wrote: > > Hi guys, > > FYI, I'm almost done to prepare new Decanter and Cellar releases. > > I will move forward with the votes during the weekend. > > After these releases, I propose to move forward on the subprojects > cleanup (cave, ...) as we discussed on the mailing list. > > I will keep you posted. > > Regards > JB
Re: Towards releases
Hi guys, I'm resuming the work on: - Karaf runtime releases preparation - Karaf Decanter & Cellar releases - Remove Winegrower and Cave from website I will keep you posted asap. Regards JB On Thu, Jan 26, 2023 at 8:31 AM Jean-Baptiste Onofré wrote: > > Hi guys, > > FYI, I'm almost done to prepare new Decanter and Cellar releases. > > I will move forward with the votes during the weekend. > > After these releases, I propose to move forward on the subprojects > cleanup (cave, ...) as we discussed on the mailing list. > > I will keep you posted. > > Regards > JB
Re: [ANN] Pax Web 8.0.18 and 9.0.7 released
Thanks ! I'm updating/testing in Karaf. Regards JB On Thu, Mar 23, 2023 at 6:43 PM Grzegorz Grzybek wrote: > > Hello > > I'd like to announce new minor releases of Pax Web: 8.0.18 and 9.0.7. > > Current runtime versions are: > > Jetty 9.4.51.v20230217 (8.0.x) and 10.0.14 (9.0.x) > Tomcat 9.0.73 > Undertow 2.2.23.Final > > There's new Karaf feature called "pax-web-jetty-http2-extras" which includes > additional, client-side http2 Jetty bundles. And existing > "pax-web-jetty-extras" feature contains two additional Jetty bundles. > > For completeness, the changelogs is available for 8.0.18[1] and 9.0.7[2]. > > kind regards > Grzegorz Grzybek > === > [1]: https://github.com/ops4j/org.ops4j.pax.web/milestone/241?closed=1 > [2]: https://github.com/ops4j/org.ops4j.pax.web/milestone/242?closed=1 > > -- > -- > -- > OPS4J - http://www.ops4j.org - op...@googlegroups.com > > --- > You received this message because you are subscribed to the Google Groups > "OPS4J" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ops4j+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ops4j/CAAdXmhqoYkihzgDHv%3DMBW5d5Unaddq1E0Ozty-PHf0_GAKZq7g%40mail.gmail.com.
Re: Board Report for March 2023
FYI, the report has been submitted to the board, including your comments. Thanks, Regards JB On Mon, Mar 6, 2023 at 2:10 PM Jean-Baptiste Onofré wrote: > > Hi guys, > > I prepared the board report for this month: > > https://cwiki.apache.org/confluence/display/KARAF/Board+Reports > > Please take a look if it's OK for you. I would like to submit the report asap. > > Thanks ! > Regards > JB
Re: Board Report for March 2023
Hi Good point about Cave and Winegrower. For Camel-Karaf, I'm not sure if it should be part of the Karaf board report. I was assuming it's more a Camel board report topic. No problem to add a section about that if everyone agree. Regards JB On Mon, Mar 6, 2023 at 2:29 PM Francois Papon wrote: > > Hi JB, > > I think we could add some notes about: > > - moving subprojects Cave and Winegrower to attic > > - result of the discussion about the Camel-Karaf governance move failed > from Camel to Karaf after the announce of the Camel team to not support > OSGi and Karaf anymore starting to Camel 4. > > regards, > > François > > On 06/03/2023 14:18, Grzegorz Grzybek wrote: > > +1 > > > > Thanks! > > > > regards > > Grzegorz Grzybek > > > > pon., 6 mar 2023 o 14:10 Jean-Baptiste Onofré > > napisał(a): > > > >> Hi guys, > >> > >> I prepared the board report for this month: > >> > >> https://cwiki.apache.org/confluence/display/KARAF/Board+Reports > >> > >> Please take a look if it's OK for you. I would like to submit the report > >> asap. > >> > >> Thanks ! > >> Regards > >> JB > >>
Board Report for March 2023
Hi guys, I prepared the board report for this month: https://cwiki.apache.org/confluence/display/KARAF/Board+Reports Please take a look if it's OK for you. I would like to submit the report asap. Thanks ! Regards JB
Re: Towards releases
Hi, I would do the website update first, and the repos later (as I did for EIK back the days). On it. Regards JB On Wed, Mar 1, 2023 at 7:37 AM Francois Papon wrote: > > Hi, > > What about subprojects cleanup? > > The plan is to move the repo into readonly mode and update the Karaf > website? > > regards, > > François > > On 01/03/2023 08:21, Jean-Baptiste Onofré wrote: > > Hi, > > > > Quick update about our releases. > > > > As you probably know, Decanter 2.10.0 has been released. Now, we will > > move forward on Decanter 3.0.0. > > > > Cellar 4.4.x is in preparation, supporting Karaf 4.4.x and containing > > mostly dependency updates. Cellar refactorings will start soon. > > > > In the meantime, Karaf runtime releases are in preparation with new > > integration distribution and new features. > > > > Stay tuned! > > > > Regards > > JB > > > > On Thu, Jan 26, 2023 at 7:31 AM Jean-Baptiste Onofré > > wrote: > >> Hi guys, > >> > >> FYI, I'm almost done to prepare new Decanter and Cellar releases. > >> > >> I will move forward with the votes during the weekend. > >> > >> After these releases, I propose to move forward on the subprojects > >> cleanup (cave, ...) as we discussed on the mailing list. > >> > >> I will keep you posted. > >> > >> Regards > >> JB
Re: Towards releases
Hi, Quick update about our releases. As you probably know, Decanter 2.10.0 has been released. Now, we will move forward on Decanter 3.0.0. Cellar 4.4.x is in preparation, supporting Karaf 4.4.x and containing mostly dependency updates. Cellar refactorings will start soon. In the meantime, Karaf runtime releases are in preparation with new integration distribution and new features. Stay tuned! Regards JB On Thu, Jan 26, 2023 at 7:31 AM Jean-Baptiste Onofré wrote: > > Hi guys, > > FYI, I'm almost done to prepare new Decanter and Cellar releases. > > I will move forward with the votes during the weekend. > > After these releases, I propose to move forward on the subprojects > cleanup (cave, ...) as we discussed on the mailing list. > > I will keep you posted. > > Regards > JB
[ANN] Apache Karaf Decanter 2.10.0 has been released!
The Apache Karaf team is pleased to announce Apache Karaf Decanter 2.10.0 release. This release is a maintenance release on the Decanter 2.x series, bringing a lot of changes, especially: - a new config allows to define default key in the split parser - fix a ClassCastException in split parser - a bunch of dependency updates You can find details on the Release Notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12351427 You can find source distribution and installation instructions here: https://karaf.apache.org/download.html Enjoy ! Regards --- The Apache Karaf team
[RESULT][VOTE] Apache Karaf Decanter 2.10.0 release
Hi, this vote passed with the following result: +1 (binding): JB Onofré, François Papon, Jamie Goodyear I'm promoting the artifacts on Maven Central and dist.apache.org, I will update Jira and the website, and I will send the announcement. Thanks all for your vote! Regards JB On Mon, Feb 20, 2023 at 6:46 PM Jean-Baptiste Onofré wrote: > > Hi everyone, > > I submit Apache Karaf Decanter 2.10.0 release to your vote. > > This release is a maintenance release bringing a lot of changes, especially: > - a new config allows to define default key in the split parser > - fix a ClassCastException in split parser > - a bunch of dependency updates > > You can take a look on the Release Notes for details: > https://repository.apache.org/content/repositories/orgapachekaraf-1184/ > > Maven Staging Repository: > https://repository.apache.org/content/repositories/orgapachekaraf-1184/ > > Dist Staging Repository: > https://dist.apache.org/repos/dist/dev/karaf/decanter/2.10.0/ > > Git tag: > decanter-2.10.0 > > Please vote to approve this release: > [ ] +1 Approve the release > [ ] -1 Don't approve the release (please provide specific comments) > > This vote will be open for at least 72 hours. > > Regards > JB
Re: [VOTE] Apache Karaf Decanter 2.10.0 release
+1 (binding) Regards JB On Mon, Feb 20, 2023 at 6:46 PM Jean-Baptiste Onofré wrote: > > Hi everyone, > > I submit Apache Karaf Decanter 2.10.0 release to your vote. > > This release is a maintenance release bringing a lot of changes, especially: > - a new config allows to define default key in the split parser > - fix a ClassCastException in split parser > - a bunch of dependency updates > > You can take a look on the Release Notes for details: > https://repository.apache.org/content/repositories/orgapachekaraf-1184/ > > Maven Staging Repository: > https://repository.apache.org/content/repositories/orgapachekaraf-1184/ > > Dist Staging Repository: > https://dist.apache.org/repos/dist/dev/karaf/decanter/2.10.0/ > > Git tag: > decanter-2.10.0 > > Please vote to approve this release: > [ ] +1 Approve the release > [ ] -1 Don't approve the release (please provide specific comments) > > This vote will be open for at least 72 hours. > > Regards > JB
[VOTE] Apache Karaf Decanter 2.10.0 release
Hi everyone, I submit Apache Karaf Decanter 2.10.0 release to your vote. This release is a maintenance release bringing a lot of changes, especially: - a new config allows to define default key in the split parser - fix a ClassCastException in split parser - a bunch of dependency updates You can take a look on the Release Notes for details: https://repository.apache.org/content/repositories/orgapachekaraf-1184/ Maven Staging Repository: https://repository.apache.org/content/repositories/orgapachekaraf-1184/ Dist Staging Repository: https://dist.apache.org/repos/dist/dev/karaf/decanter/2.10.0/ Git tag: decanter-2.10.0 Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Don't approve the release (please provide specific comments) This vote will be open for at least 72 hours. Regards JB
[CANCEL] [VOTE] Accept karaf-camel as new Apache Karaf subproject
Hi guys, According to the vote and discussion on this thread, we don't have a consensus to move camel-karaf into the Karaf community. 1. As we have a decent/large number of users on Karaf running Camel routes. 2. As the Camel "core" community doesn't want to maintain OSGi related stuff in camel-core. I propose the following: 1. We keep camel-karaf at Camel (as we have camel-quarkus, camel-spring-boot, ..., I hope we don't have anything in camel-core needed/required by camel-quarkus or camel-spring-boot, else it wouldn't be fair for camel-karaf ;) ) 2. Camel Core can remove OSGi related stuff (headers, maven-bundle-plugin, ...), we will implement a new approach in camel-karaf (with a custom deployer as I proposed before for instance). 3. I will do a complete cleanup on the camel-karaf main branch, already upgrading to camel 4 to prepare camel-karaf 4. Thoughts ? Regards JB
Towards releases
Hi guys, FYI, I'm almost done to prepare new Decanter and Cellar releases. I will move forward with the votes during the weekend. After these releases, I propose to move forward on the subprojects cleanup (cave, ...) as we discussed on the mailing list. I will keep you posted. Regards JB
