[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=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=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=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=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=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=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=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
> ~[?:?] > ... 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=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=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=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=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=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=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=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=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=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
Re: [PROPOSAL] Create integration (ServiceMix like) distribution in Karaf OSGi runtime
Hi, Fair point, the initial intent is "just" to have https://github.com/apache/servicemix/tree/master/assemblies/apache-servicemix like distribution in as apache-karaf-integration. The users can build their custom distributions based on karaf minimal, karaf standard, karaf integration. Another option is not to create a full distribution, but features repositories only and let user do the assembly. However, a lot of SMX users don't want to create custom distro: they just want to extract & run and then deploy their artifacts (ok, they are probably "old" style :)). Probably the option would be to have ready to use features repositories, and "document" (or eventually add tool) how to use it. Regards JB On Thu, Jan 19, 2023 at 10:42 AM Romain Manni-Bucau wrote: > > Hi JB, > > Whereas I can understand the intent I also see it will be hard because: > > 1. Default distro never matches well (even smix got custom distro) > 2. Features are there for that exact need > > If I rephrase my point I guess the request looks more like "get us back what > vendors abandon" but this was mainly about support and contracts, here we'll > not get that so it looks to me we already provide that: karaf + features (+ > optionally custom build if really needed). > Not sticking to that sounds like you will get like hundreds of distro - > without thinking too hard I see: > * cloud one (prometheus/health/log/...) > * jaxrs whiteboard > * jaxrs whiteboard + jpa (web profile like) > * http whiteboard only > * amq > * amq + jpa > * kafka > * kafka + jpa > * pulsar > * pulsar + jpa > * ... > (and all potential matrix) > > Since features were designed to avoid that I think it makes sens to avoid to > go that path, it would also be consistent with the cloud spirit - even if the > move is not actual most companies target some cloud mindset, in particular a > better dep control - which means lighter distros. > > > Hope it makes sense. > > Romain Manni-Bucau > @rmannibucau | Blog | Old Blog | Github | LinkedIn | Book > > > Le jeu. 19 janv. 2023 à 09:27, Jean-Baptiste Onofré a > écrit : >> >> Hi Romain, >> >> It's a request to move "natively" to Karaf: most SMX users already >> moved to Karaf, but they asked for a ready to go distribution. The few >> SMX uses are looking for a similar distribution in Karaf (just to >> avoid creating a distribution themselves). >> >> So, I see more as a new distribution in the Karaf OSGi runtime project >> than a new subproject. >> >> Regards >> JB >> >> On Wed, Jan 18, 2023 at 1:49 PM Romain Manni-Bucau >> wrote: >> > >> > Hi JB, >> > >> > Is there a community behind or did people already moved to Karaf so this is >> > just about killing smix project officially. >> > >> > Trying to see if it is mainly about having really itests and enriching >> > features.xml (theorically nothing new) or creating a new distro and almost >> > a subproject. >> > >> > >> > Le mer. 18 janv. 2023 à 13:44, Jean-Baptiste Onofré a >> > écrit : >> > >> > > Hi guys, >> > > >> > > The ServiceMix community is discussing about moving most of the SMX >> > > parts into Karaf (the useful parts ;) ). >> > > >> > > As part of this move, the "main" ServiceMix distribution is mainly a >> > > Karaf assembly. >> > > >> > > Currently, we have two distributions: "standard" >> > > (apache-karaf-x.x.x.tar.gz) and "minimal" >> > > (apache-karaf-minimal-x.x.x.tar.gz). >> > > >> > > I propose to add a new distribution (in assemblies): >> > > apache-karaf-integration-x.x.x.tar.gz containing ready to go >> > > Karaf/Camel/CXF/ActiveMQ smooth integration. >> > > Concretely, it means: >> > > - we will have integration features repository XML >> > > - we will have a distribution based on this features repository >> > > - we will have itest on this distribution with the best coverage we can >> > > >> > > If there is no objection, I will create the Jira and create a PR (as I >> > > have almost all ready :)). >> > > >> > > Thoughts ? >> > > >> > > Regards >> > > JB >> > >
Re: [VOTE] Accept karaf-camel as new Apache Karaf subproject
Hi, I think it's important to split the discussion into two major aspects: technical aspect and community aspect. - Technically speaking, I don't see camel-karaf very different from camel-spring-boot or camel-quarkus or camel-k. It contains Camel specific to a platform, exactly like camel-quarkus or camel-spring-boot. The painful part is the wrapping of Camel components as features and sometimes the "impact" of OSGi on the Camel components behavior. However, I send a message while ago on the Camel dev mailing about couple of proposal to improve this, with highly simplified Camel Karaf features repository, no need to use SMX bundles anymore, no even need to wrap the Camel component as a bundle (most of the logic is done at build and camel-osgi-core). So, I think that technically speaking, we have room to improve the current situation and for me it's not a blocker. - Now about the community. I think we have to say things clearly: we know that the company mainly contributing on Camel doesn't want to support Karaf/OSGi anymore, due to roadmap change and business perspective. That's fair and fully understable. Where we have to be careful is that, as Apache project, if the community still wants to contribute and maintain Camel Karaf in Camel project, it's also a fair request, and this company should be supportive of that (and not "block" this community driven decision). Since the beginning of this discussion, I have tried to find a consensus matching everyone's expectation and wish (that's one of the core values of the Apache way). I thought the different communities wanted to move Camel Karaf to Karaf. But this thread shows it's not the case for everyone. So, I think it makes sense to cancel the formal vote now and start a new discussion round. If we don't have consensus about the move, then we will focus on the first point: keeping camel-karaf at camel and improving use/maintenance/etc from a technical standpoint. Thoughts ? Regards JB On Wed, Jan 18, 2023 at 9:14 PM Andrea Cosentino wrote: > > As a side note, it's not only aligning the features, it's also upgrading > the servicemix bundles to be able to align, JB knows what I'm talking about. > > I helped there a lot too (less in the last year or so) and it's really a > mess. > > Il mer 18 gen 2023, 20:43 Romain Manni-Bucau ha > scritto: > > > Le mer. 18 janv. 2023 à 20:17, Andrea Cosentino a > > écrit : > > > > > Il mer 18 gen 2023, 20:06 Romain Manni-Bucau ha > > > scritto: > > > > > > > Le mer. 18 janv. 2023 à 19:43, Andrea Cosentino a > > > > écrit : > > > > > > > > > Hello, > > > > > > > > > > The point is just one in relation to OSGi metadata. The components > > will > > > > be > > > > > consumed, also, by runtimes that don't need OSGi metadata, so why all > > > the > > > > > components should be with OSGi metadata and packaged as bundles? > > > > > > > > > > > > > I'm maybe a bit dumb but why all the work and meta for quarkus and > > spring > > > > boot if the reasoning is right? > > > > I perfectly understand spring or quarkus have their own programming > > > > model/runtime so need specific code and meta but then how is OSGi > > > > different? > > > > > > > > A simple example is that you should be able to drop most jandex indices > > > if > > > > your statement is true. > > > > > > > > > > My point is related more to have the components as bundles with OSGi > > > metadata. To me they should be just JAR. > > > Mainly the reason I'm saying this about supporting camel-karaf because > > > the work wi be on the shoulders of 1 developer and this is not right for > > me > > > and for the community. > > > > > > > Sure but osgi bundles always had been designed to be just jars as much as a > > jar with a jandex index or even with a custom manifest metadata or a json > > containing the pom description ;). > > > > But I fully share with you the ownership point. > > Any bundle (more generally meta maintenance) should be owned by the core > > code writer otherwise we end in weird state all the time, in particular > > when parts are optionals or need some specific loading mecanism > > (serviceloader for ex). The lifecycle is also an issue in time, we already > > are there with features around whiteboards for ex and camel itself has a > > hard time ensuring components work together so fear camel can be a bit big > > to have this enrichment work done properly outside camel in a project with > > less task force than camel itself. > > > > > > > Just this. > > > > > > > > > > > > > > > > > > > > > I don't see the reason why. At least the OSGi metadata should be > > > > generated > > > > > under camel Karaf project, instead of being part of the core > > components > > > > > > > > > > > > > I think the exact opposite since handling metadata in a 3rd always got > > > > proven not working very well for end user. > > > > SMix did a bunch of forks for that reason - which was enabling users > > but > > > > also a big constrait since users were not able to use
Re: [PROPOSAL] Create integration (ServiceMix like) distribution in Karaf OSGi runtime
Hi Romain, It's a request to move "natively" to Karaf: most SMX users already moved to Karaf, but they asked for a ready to go distribution. The few SMX uses are looking for a similar distribution in Karaf (just to avoid creating a distribution themselves). So, I see more as a new distribution in the Karaf OSGi runtime project than a new subproject. Regards JB On Wed, Jan 18, 2023 at 1:49 PM Romain Manni-Bucau wrote: > > Hi JB, > > Is there a community behind or did people already moved to Karaf so this is > just about killing smix project officially. > > Trying to see if it is mainly about having really itests and enriching > features.xml (theorically nothing new) or creating a new distro and almost > a subproject. > > > Le mer. 18 janv. 2023 à 13:44, Jean-Baptiste Onofré a > écrit : > > > Hi guys, > > > > The ServiceMix community is discussing about moving most of the SMX > > parts into Karaf (the useful parts ;) ). > > > > As part of this move, the "main" ServiceMix distribution is mainly a > > Karaf assembly. > > > > Currently, we have two distributions: "standard" > > (apache-karaf-x.x.x.tar.gz) and "minimal" > > (apache-karaf-minimal-x.x.x.tar.gz). > > > > I propose to add a new distribution (in assemblies): > > apache-karaf-integration-x.x.x.tar.gz containing ready to go > > Karaf/Camel/CXF/ActiveMQ smooth integration. > > Concretely, it means: > > - we will have integration features repository XML > > - we will have a distribution based on this features repository > > - we will have itest on this distribution with the best coverage we can > > > > If there is no objection, I will create the Jira and create a PR (as I > > have almost all ready :)). > > > > Thoughts ? > > > > Regards > > JB > >
Re: [VOTE] Accept karaf-camel as new Apache Karaf subproject
Correct, I mentioned this in my previous email (camel-karaf to karaf-camel). Regards JB On Wed, Jan 18, 2023 at 1:26 PM Claus Ibsen wrote: > > Hi > > And the source code java package names needs to be migrated as well > org.apache.camel.karaf -> org.apache.karaf.camel > > And documentation is moved over to Apache Karaf, where the karaf camel > releases its own new set of documentation/website. > > The existing Camel Karaf 3.x will be maintained as-is until its EOL. > > > > > > On Wed, Jan 18, 2023 at 12:14 PM Claus Ibsen wrote: > > > Hi > > > > This SHOULD also mean that the project should be known as karaf-camel > > AND that the artifacts released for download and maven central should have > > changed GAVs > > > > groupId = org.apache.karaf.camel > > artifactId = karaf-camel-xxx > > version = x.y.z > > > > For version then it may want to follow the Camel version, eg 4.0.0 > > > > > > > > > > > > > > On Wed, Jan 18, 2023 at 11:03 AM Jean-Baptiste Onofré > > wrote: > > > >> Hi guys, > >> > >> The Apache Camel community proposed to move Camel Karaf to the Apache > >> Karaf project (as a new subproject). > >> > >> As a reminder, Camel Karaf provides: > >> - support Camel Contexts/Routes as OSGi services (camel-core-osgi) > >> - Camel components specific to OSGi and Karaf (camel-blueprint, > >> camel-scr, ...) > >> - wrapping of Camel components as Karaf features (providing a features > >> repository XML) > >> > >> I think there are a bunch of users using camel-karaf, so, from a > >> community perspective, it would be great to maintain it. > >> Furthermore, I already have some ideas to improve karaf-camel, like > >> avoiding to wrap each Camel component as an OSGi bundle, but instead > >> creating a kind of Uber jar to simplify deployment and have more > >> reliable behavior. > >> > >> Concretely, accepting camel-karaf as Karaf subproject would mean: > >> - maintain the existing code, and improving it, preparing kind of > >> roadmap for camel-karaf > >> - deal with Camel versions and components (and all difficulties that > >> it could cause in an OSGi context :) ) > >> - maintain camel-karaf specific documentation > >> - vote for the releases (the PMC members would be the Karaf ones, so > >> binding vote from Karaf PMC members) > >> > >> I submit accepting camel-karaf (so karaf-camel :)) as new Karaf > >> subproject to your vote: > >> > >> Please vote to approve this release: > >> [ ] +1 Approve camel-karaf as new Karaf subproject > >> [ ] -1 Don't approve camel-karaf as new Karaf subproject (please > >> provide specific comments) > >> > >> This vote will be open for at least 72 hours. > >> > >> Thanks, > >> Regards > >> JB > >> > > > > > > -- > > Claus Ibsen > > - > > @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2
[PROPOSAL] Create integration (ServiceMix like) distribution in Karaf OSGi runtime
Hi guys, The ServiceMix community is discussing about moving most of the SMX parts into Karaf (the useful parts ;) ). As part of this move, the "main" ServiceMix distribution is mainly a Karaf assembly. Currently, we have two distributions: "standard" (apache-karaf-x.x.x.tar.gz) and "minimal" (apache-karaf-minimal-x.x.x.tar.gz). I propose to add a new distribution (in assemblies): apache-karaf-integration-x.x.x.tar.gz containing ready to go Karaf/Camel/CXF/ActiveMQ smooth integration. Concretely, it means: - we will have integration features repository XML - we will have a distribution based on this features repository - we will have itest on this distribution with the best coverage we can If there is no objection, I will create the Jira and create a PR (as I have almost all ready :)). Thoughts ? Regards JB
Re: [VOTE] Accept karaf-camel as new Apache Karaf subproject
Hi Andrea, yes, thanks. I forgot to mention that the move if for Camel 4.x (not the existing branch/version). Regards JB On Wed, Jan 18, 2023 at 11:05 AM Andrea Cosentino wrote: > > As as side note to what JB just wrote: > > as Apache Camel community we'll still maintain the 3.x side of the > projects, for continuity, Karaf-camel will be the house for the Camel 4.x > OSGi support. > > Thanks. > > Il giorno mer 18 gen 2023 alle ore 11:03 Jean-Baptiste Onofré < > j...@nanthrax.net> ha scritto: > > > Hi guys, > > > > The Apache Camel community proposed to move Camel Karaf to the Apache > > Karaf project (as a new subproject). > > > > As a reminder, Camel Karaf provides: > > - support Camel Contexts/Routes as OSGi services (camel-core-osgi) > > - Camel components specific to OSGi and Karaf (camel-blueprint, camel-scr, > > ...) > > - wrapping of Camel components as Karaf features (providing a features > > repository XML) > > > > I think there are a bunch of users using camel-karaf, so, from a > > community perspective, it would be great to maintain it. > > Furthermore, I already have some ideas to improve karaf-camel, like > > avoiding to wrap each Camel component as an OSGi bundle, but instead > > creating a kind of Uber jar to simplify deployment and have more > > reliable behavior. > > > > Concretely, accepting camel-karaf as Karaf subproject would mean: > > - maintain the existing code, and improving it, preparing kind of > > roadmap for camel-karaf > > - deal with Camel versions and components (and all difficulties that > > it could cause in an OSGi context :) ) > > - maintain camel-karaf specific documentation > > - vote for the releases (the PMC members would be the Karaf ones, so > > binding vote from Karaf PMC members) > > > > I submit accepting camel-karaf (so karaf-camel :)) as new Karaf > > subproject to your vote: > > > > Please vote to approve this release: > > [ ] +1 Approve camel-karaf as new Karaf subproject > > [ ] -1 Don't approve camel-karaf as new Karaf subproject (please > > provide specific comments) > > > > This vote will be open for at least 72 hours. > > > > Thanks, > > Regards > > JB > >
[VOTE] Accept karaf-camel as new Apache Karaf subproject
Hi guys, The Apache Camel community proposed to move Camel Karaf to the Apache Karaf project (as a new subproject). As a reminder, Camel Karaf provides: - support Camel Contexts/Routes as OSGi services (camel-core-osgi) - Camel components specific to OSGi and Karaf (camel-blueprint, camel-scr, ...) - wrapping of Camel components as Karaf features (providing a features repository XML) I think there are a bunch of users using camel-karaf, so, from a community perspective, it would be great to maintain it. Furthermore, I already have some ideas to improve karaf-camel, like avoiding to wrap each Camel component as an OSGi bundle, but instead creating a kind of Uber jar to simplify deployment and have more reliable behavior. Concretely, accepting camel-karaf as Karaf subproject would mean: - maintain the existing code, and improving it, preparing kind of roadmap for camel-karaf - deal with Camel versions and components (and all difficulties that it could cause in an OSGi context :) ) - maintain camel-karaf specific documentation - vote for the releases (the PMC members would be the Karaf ones, so binding vote from Karaf PMC members) I submit accepting camel-karaf (so karaf-camel :)) as new Karaf subproject to your vote: Please vote to approve this release: [ ] +1 Approve camel-karaf as new Karaf subproject [ ] -1 Don't approve camel-karaf as new Karaf subproject (please provide specific comments) This vote will be open for at least 72 hours. Thanks, Regards JB
[ANN] Apache Karaf OSGi runtime 4.3.9 has been released!p
The Apache Karaf team is pleased to announce Apache Karaf OSGi runtime 4.3.9 release. This is a maintenance release, bringing a lot of dependency updates and fixes, especially: - fix threads leak in karaf-maven-plugin:verify goal - fix JMX RmiServer stub IP address assignation - add shell:alias and instance:package shell commands - fix SSH client on Windows - a lot of dependency updates - and much more! You can have the detailed Release Notes here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12352383 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.9 release
Hi all, this vote passed with the following result: +1 (binding): Freeman Fang, Jamie Goodyear, François Papon, JB Onofré, Grzegorz Grzybek +1 (non binding): Matt Pavlovich I'm promoting the artifacts on Maven Central and dist.apache.org, then I will update Jira and prepare an announcement. Thanks all for your vote! Regards JB On Tue, Jan 10, 2023 at 6:41 PM Jean-Baptiste Onofré wrote: > > Hi guys, > > I submit Apache Karaf OSGi runtime 4.3.9 release to your vote. > > This release is a maintenance release bringing a lot of dependency > updates and fixes. > Especially, this release includes: > - fix threads leak in karaf-maven-plugin (in verify feature goal) > - fix on JMX stub IP address assignation (especially on different > docker networks) > - re-add shell:alias command > - fix ssh client on Windows > - and several dependency updates ! > > You can take a look on the Release Notes for details: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12352383 > > Maven Staging Repository: > https://repository.apache.org/content/repositories/orgapachekaraf-1183/ > > Dist Staging Repository: > https://dist.apache.org/repos/dist/dev/karaf/4.3.9/ > > Git tag: > karaf-4.3.9 > > 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.3 released !
The Apache Karaf team is pleased to announce Apache Karaf OSGi runtime 4.4.3 release. This release is a maintenance release bringing a lot of dependency updates and fixes. Especially, this release includes: - fix threads leak in karaf-maven-plugin (in verify feature goal) - fix on JMX stub IP address assignation (especially on different docker networks) - re-add shell:alias command - fix ssh client on Windows - upgrade to Aries JAX RS Whiteboard 2.0.2 - upgrade to Pax Web 8.0.15 - and several dependency updates ! You can take a look on the Release Notes for details: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12352267 You can download this release: https://karaf.apache.org/download.html Enjoy! The Apache Karaf team
Re: karaf-4.5.x?
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: [DISCUSS] Apache Karaf subprojects Roadmap
Hi, Yes, we need a vote from the Karaf community. I will start it tonight or tomorrow morning. Regards JB On Thu, Jan 12, 2023 at 5:08 PM Francois Papon wrote: > > Hi JB, > > As the work to move main branch of Camel to V4 is on the way right now, > do we need to start a vote on Karaf mailing list to approve or not the > move of Camel-Karaf under the umbrella of Karaf as a new subproject? > > regards, > > François > > On 10/01/2023 13:53, Jean-Baptiste Onofré wrote: > > Following this thread, I propose to start a vote to move Cave and > > Winegrower to "attic" (basically, removing mentions on website and > > announcing "not active" state). > > > > Regards > > JB > > > > On Mon, Jan 9, 2023 at 10:19 AM fpapon wrote: > >> Hi JB, > >> > >> Make sense for Cave and Winegrower. > >> > >> About Camel-Karaf, as it was announced by the Camel team in the roadmap > >> to Camel 4, I was thinking that it was already acted: > >> > >> https://camel.apache.org/blog/2023/01/camel4roadmap/ > >> > >> I asked the question about the OSGi bundle still provide or not by Camel > >> team but no clear decision, Camel team don't want to provide OSGi bundle > >> for Camel core anymore. > >> > >> regards, > >> > >> François > >> > >> On 09/01/2023 10:13, Jean-Baptiste Onofré wrote: > >>> Hi François, > >>> > >>> Thanks for bringing this discussion. > >>> > >>> Here's my personal standpoint: > >>> 1. Decanter: I started to work on Decanter 3.x (refactoring). I think > >>> we can do a release now with just updates on the collectors/appenders > >>> before moving forward on decanter 3.x. I propose to cut new Decanter > >>> release asap. > >>> 2. Cellar: quite the same as Decanter. I plan a refactoring, but it is > >>> worth doing an updated version (new hazelcast, kubernetes client, > >>> karaf version). Same: I propose to cut new Cellar release asp. > >>> 3. Cave: I think we don't have many users on Cave, maybe it's worth to > >>> move the project to "attic" ? > >>> 4. Winegrower: same as Cave, I don't think we have a lot of users, > >>> maybe it's worth to move the project to "attic" ? > >>> 5. Minho: > >>> 6. For SMX bundles, the objective is not to move as it is. The > >>> objective it's to use the new bundle descriptor I started in Pax URL. > >>> Karaf "Bundles" will host just the descriptor to create the bundle on > >>> the fly (and eventually cached). The other part of SMX (assembly + > >>> spec) can be moved in Karaf subproject. > >>> 7. For camel-karaf, I'm open to community proposals. If it's better to > >>> have it in Karaf, I'm OK with it (same question about jclouds-karaf). > >>> > >>> Regards > >>> JB > >>> > >>> On Mon, Jan 9, 2023 at 10:07 AM fpapon wrote: > >>>> Hi, > >>>> > >>>> I want to start a thread about Apache Karaf subprojects roadmap and > >>>> maintainability. > >>>> > >>>> Today we have: > >>>> > >>>> - Decanter: last release on Feb. 2022 > >>>> > >>>> - Cellar: last release on Aug. 2020 > >>>> > >>>> - Cave: last release on Nov. 2019 > >>>> > >>>> We also have: > >>>> > >>>> - Winegrower: last release on Nov. 2020 > >>>> > >>>> - Minho: last release on Jan. 2023 (but plan to move to dedicated TLP > >>>> project) > >>>> > >>>> There is also some discussion about moving SMX bundle and Camel-Karaf as > >>>> Karaf subprojects so I think it will be nice to see what we would/could > >>>> maintain. > >>>> > >>>> regards, > >>>> > >>>> -- > >>>> -- > >>>> François > >>>> > >> -- > >> -- > >> François > >>
Re: [DISCUSS] Apache Karaf subprojects Roadmap
Hi Steven, I'm still working on the first tangible code to share. I'm busy with some Karaf releases (decanter and cellar), I will share details soon. Regards JB On Thu, Jan 12, 2023 at 8:34 AM Steven Huypens wrote: > > Hi JB, > > Where can I find more info on this ? And can it be used already ? > > Best regards, > Steven > > On Tue, Jan 10, 2023 at 1:52 PM Jean-Baptiste Onofré > wrote: > > > Hi Greg, > > > > yes, I introduced a new smx: protocol handler that takes a json > > descriptor. This json descriptor contains: > > - source artifacts > > - OSGi headers > > - eventually transformers (for META-INF/services, MANIFEST, etc) > > > > Regards > > JB > > > > On Mon, Jan 9, 2023 at 10:30 AM Grzegorz Grzybek > > wrote: > > > > > > Hello > > > > > > I'd like to ask about: > > > > > > For SMX bundles, the objective is not to move as it is. The > > > > objective it's to use the new bundle descriptor I started in Pax URL. > > > > Karaf "Bundles" will host just the descriptor to create the bundle on > > > > the fly (and eventually cached). The other part of SMX (assembly + > > > > spec) can be moved in Karaf subproject. > > > > > > > > > > I know that providing OSGi metadata to external 3rd party libs which do > > not > > > care about OSGi is a bit PITA... (I remember back in theserverside.com > > days > > > I suggested using external metadata instead of one kept in > > > META-INF/MANIFEST.MF...) > > > How do you imagine this on the fly generation? kind of like wrap: > > protocol? > > > > > > regards > > > Grzegorz Grzybek > > > > > > pon., 9 sty 2023 o 10:20 fpapon napisał(a): > > > > > > > Hi JB, > > > > > > > > Make sense for Cave and Winegrower. > > > > > > > > About Camel-Karaf, as it was announced by the Camel team in the roadmap > > > > to Camel 4, I was thinking that it was already acted: > > > > > > > > https://camel.apache.org/blog/2023/01/camel4roadmap/ > > > > > > > > I asked the question about the OSGi bundle still provide or not by > > Camel > > > > team but no clear decision, Camel team don't want to provide OSGi > > bundle > > > > for Camel core anymore. > > > > > > > > regards, > > > > > > > > François > > > > > > > > On 09/01/2023 10:13, Jean-Baptiste Onofré wrote: > > > > > Hi François, > > > > > > > > > > Thanks for bringing this discussion. > > > > > > > > > > Here's my personal standpoint: > > > > > 1. Decanter: I started to work on Decanter 3.x (refactoring). I think > > > > > we can do a release now with just updates on the collectors/appenders > > > > > before moving forward on decanter 3.x. I propose to cut new Decanter > > > > > release asap. > > > > > 2. Cellar: quite the same as Decanter. I plan a refactoring, but it > > is > > > > > worth doing an updated version (new hazelcast, kubernetes client, > > > > > karaf version). Same: I propose to cut new Cellar release asp. > > > > > 3. Cave: I think we don't have many users on Cave, maybe it's worth > > to > > > > > move the project to "attic" ? > > > > > 4. Winegrower: same as Cave, I don't think we have a lot of users, > > > > > maybe it's worth to move the project to "attic" ? > > > > > 5. Minho: > > > > > 6. For SMX bundles, the objective is not to move as it is. The > > > > > objective it's to use the new bundle descriptor I started in Pax URL. > > > > > Karaf "Bundles" will host just the descriptor to create the bundle on > > > > > the fly (and eventually cached). The other part of SMX (assembly + > > > > > spec) can be moved in Karaf subproject. > > > > > 7. For camel-karaf, I'm open to community proposals. If it's better > > to > > > > > have it in Karaf, I'm OK with it (same question about jclouds-karaf). > > > > > > > > > > Regards > > > > > JB > > > > > > > > > > On Mon, Jan 9, 2023 at 10:07 AM fpapon wrote: > > > > >> Hi, > > > > >> > > > > >> I want to start a thread about Apache Karaf subprojects roadmap and > > > > >> maintainability. > > > > >> > > > > >> Today we have: > > > > >> > > > > >> - Decanter: last release on Feb. 2022 > > > > >> > > > > >> - Cellar: last release on Aug. 2020 > > > > >> > > > > >> - Cave: last release on Nov. 2019 > > > > >> > > > > >> We also have: > > > > >> > > > > >> - Winegrower: last release on Nov. 2020 > > > > >> > > > > >> - Minho: last release on Jan. 2023 (but plan to move to dedicated > > TLP > > > > >> project) > > > > >> > > > > >> There is also some discussion about moving SMX bundle and > > Camel-Karaf as > > > > >> Karaf subprojects so I think it will be nice to see what we > > would/could > > > > >> maintain. > > > > >> > > > > >> regards, > > > > >> > > > > >> -- > > > > >> -- > > > > >> François > > > > >> > > > > -- > > > > -- > > > > François > > > > > > > > > >
Re: [VOTE] Apache Karaf OSGi runtime 4.3.9 release
+1 (binding) Regards JB On Tue, Jan 10, 2023 at 6:41 PM Jean-Baptiste Onofré wrote: > > Hi guys, > > I submit Apache Karaf OSGi runtime 4.3.9 release to your vote. > > This release is a maintenance release bringing a lot of dependency > updates and fixes. > Especially, this release includes: > - fix threads leak in karaf-maven-plugin (in verify feature goal) > - fix on JMX stub IP address assignation (especially on different > docker networks) > - re-add shell:alias command > - fix ssh client on Windows > - and several dependency updates ! > > You can take a look on the Release Notes for details: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12352383 > > Maven Staging Repository: > https://repository.apache.org/content/repositories/orgapachekaraf-1183/ > > Dist Staging Repository: > https://dist.apache.org/repos/dist/dev/karaf/4.3.9/ > > Git tag: > karaf-4.3.9 > > 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.9 release
Hi guys, I submit Apache Karaf OSGi runtime 4.3.9 release to your vote. This release is a maintenance release bringing a lot of dependency updates and fixes. Especially, this release includes: - fix threads leak in karaf-maven-plugin (in verify feature goal) - fix on JMX stub IP address assignation (especially on different docker networks) - re-add shell:alias command - fix ssh client on Windows - and several dependency updates ! You can take a look on the Release Notes for details: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12352383 Maven Staging Repository: https://repository.apache.org/content/repositories/orgapachekaraf-1183/ Dist Staging Repository: https://dist.apache.org/repos/dist/dev/karaf/4.3.9/ Git tag: karaf-4.3.9 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
[RESULT][VOTE] Apache Karaf OSGi runtime 4.4.3 release (take #2)
Hi, this vote passed with the following result: +1 (binding): Grzegorz Grzybek, François Papon, Jamie Goodyear, JB Onofré +1 (non binding): Robert Varga, Mark Derricutt, Steven Huypens I'm promoting the artifacts on Maven Central and dist.apache.org. Then, I will update Jira and the website, followed by an official announcement. Thanks all for your vote ! Regards JB On Sat, Jan 7, 2023 at 6:43 AM Jean-Baptiste Onofré wrote: > > Hi guys, > > I submit Apache Karaf OSGi runtime 4.4.3 release to your vote (take #2). > > This release is a maintenance release bringing a lot of dependency > updates and fixes. > Especially, this release includes: > - fix threads leak in karaf-maven-plugin (in verify feature goal) > - fix on JMX stub IP address assignation (especially on different > docker networks) > - re-add shell:alias command > - fix ssh client on Windows > - upgrade to Aries JAX RS Whiteboard 2.0.2 > - upgrade to Pax Web 8.0.15 > - and several dependency updates ! > > You can take a look on the Release Notes for details: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12352267 > > Maven Staging Repository: > https://repository.apache.org/content/repositories/orgapachekaraf-1182/ > > Dist Staging Repository: > https://dist.apache.org/repos/dist/dev/karaf/4.4.3/ > > Git tag: > karaf-4.4.3 > > 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
