Re: [VOTE] Apache Karaf OSGi runtime 4.4.3 release (take #2)
+1 (binding) 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
Re: [VOTE] Apache Karaf OSGi runtime 4.4.3 release (take #2)
+1 Cheers, Jamie On Mon, Jan 9, 2023 at 4:56 AM Francois Papon wrote: > > +1 (binding) > > Regards, > > Francois > > On 07/01/2023 06:43, 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
Re: [DISCUSS] Apache Karaf subprojects Roadmap
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: [DISCUSS] Apache Karaf subprojects Roadmap
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
[ANN] Pax Logging 2.2.1 and 1.12.4 released
Hello First - I've updated https://github.com/ops4j/org.ops4j.pax.logging#versions page which now marks only 2 versions as active. Here's more detailed explanation: - versions 1.9.x and 1.10.x are pre-refactoring versions without any real integration tests - version 1.11.x and 1.12.x are both based on OSGi CMPN Log service 1.3, but version 1.11.x includes Log4j1 backend. I've decided to keep and maintain only version 1.12.x, because we don't want to use Log4j1 backend anymore. The Log4j1 API is still available though. So please use 1.12.x for Felix 5.6 / Karaf 4.2 - version 2.0.x (with Log4j1 backend) and 2.1.x (without Log4j1 backend) are based on OSGi CMPN Log service 1.4 and because Log service 1.5 is identical, I've decided to keep and maintain only version 2.2.x The most important change in 1.12.4 and 2.2.1 is related to SLF4J 2.x API support. Actually the interfaces didn't change since version 1.7.x, but there was a change with discovery of logging backend. Instead of static org.slf4j.impl.StaticLoggerBinder, SLF4J 2 now relies on /META-INF/services/org.slf4j.spi.SLF4JServiceProvider which is now providing org.ops4j.pax.logging.slf4j.PaxLoggingSLF4JServiceProvider service. >From the API point of view nothing has changed except that pax-logging-api now exports `org.slf4j` package with version 2.0.6 (in addition to version 1.4, 1.5, 1.6 and 1.7). That's important for OSGi bundles compiled with maven-bundle-plugin (or bnd-maven-plugin) with default configuration which would generate this import header: Import-Package: org.slf4j;version="[2.0,3.0)". This would cause problems before Pax Logging 2.2.1 and 1.12.4. All the release notes can be found using the following links: - 2.2.1: https://github.com/ops4j/org.ops4j.pax.logging/milestone/98?closed=1 - 1.12.4: https://github.com/ops4j/org.ops4j.pax.logging/milestone/105?closed=1 kind regards Grzegorz Grzybek
[DISCUSS] Apache Karaf subprojects Roadmap
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
Re: [VOTE] Apache Karaf OSGi runtime 4.4.3 release (take #2)
+1 (binding) Regards, Francois On 07/01/2023 06:43, 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
Re: karaf-4.5.x?
We are still targeting code for JDK8, with JDK11 built anyway. We plan to switch to JDK 11+ only: https://issues.apache.org/jira/browse/KARAF-7499 Probably, we can plan this for 4.5.x (I planned to do it on 4.4.x, but maybe it makes more sense for 4.5.x). Regards JB On Sun, Jan 8, 2023 at 8:33 AM 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. > > > > --- > "The ease with which a change can be implemented has no relevance at all > to whether it is the right change for the (Java) Platform for all time." > Mark Reinhold. > > Mark Derricutt > http://www.chaliceofblood.net > http://www.theoryinpractice.net > http://twitter.com/talios > http://facebook.com/mderricutt > https://mastodon.nz/@talios
