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: Unable to start Pax-Web 8.0.6 by using PFX Certificate.
Hello
What is you $KARAF_HOME/etc/org.ops4j.pax.web.cfg configuration? (please
remove the password values).
regards
Grzegorz Grzybek
czw., 12 sty 2023 o 20:14 Vamsikrishna Koka
napisał(a):
> Hi Team,
>
> I have migrated karaf version 4.4.1 and OpenJDK 11 also. Tried to using
> PFX file but it was failed due to given below stack trace.
>
> Please can anyone take look at once.
>
> 2023-01-12T12:53:03.265-0500 CEF:1 | org.eclipse.jetty.util |
> 9.4.48.v20220622 | WARN | ID=245 THR=ange controller)
> CAT=AbstractLifeCycleMSG=FAILED Server@21d6680d
> {FAILED}[9.4.48.v20220622]:
> java.lang.NullPointerException
> java.lang.NullPointerException: null
> at
> org.eclipse.jetty.util.ssl.SslContextFactory.getKeyManagers(SslContextFactory.java:1249)
> ~[?:?]
> at
> org.eclipse.jetty.util.ssl.SslContextFactory$Server.getKeyManagers(SslContextFactory.java:2364)
> ~[?:?]
> at
> org.eclipse.jetty.util.ssl.SslContextFactory.load(SslContextFactory.java:373)
> ~[?:?]
> at
> org.eclipse.jetty.util.ssl.SslContextFactory.doStart(SslContextFactory.java:244)
> ~[?:?]
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
> ~[?:?]
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
> ~[?:?]
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117)
> ~[?:?]
> at
> org.eclipse.jetty.server.SslConnectionFactory.doStart(SslConnectionFactory.java:97)
> ~[?:?]
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
> ~[?:?]
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
> ~[?:?]
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117)
> ~[?:?]
> at
> org.eclipse.jetty.server.AbstractConnector.doStart(AbstractConnector.java:323)
> ~[?:?]
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:81)
> ~[?:?]
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:234)
> ~[?:?]
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
> ~[?:?]
> at org.eclipse.jetty.server.Server.doStart(Server.java:401) ~[?:?]
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
> ~[?:?]
> at
> org.ops4j.pax.web.service.jetty.internal.JettyServerWrapper.start(JettyServerWrapper.java:623)
> ~[?:?]
> at
> org.ops4j.pax.web.service.jetty.internal.JettyServerController.start(JettyServerController.java:109)
> ~[?:?]
> at
> org.ops4j.pax.web.service.internal.Activator.performConfiguration(Activator.java:551)
> ~[?:?]
> at
> org.ops4j.pax.web.service.internal.Activator.updateController(Activator.java:441)
> ~[?:?]
> at
> org.ops4j.pax.web.service.internal.Activator.lambda$updateServerControllerFactory$1(Activator.java:347)
> ~[?:?]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> ~[?:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
> ~[?:?]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> ~[?:?]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> ~[?:?]
> at java.lang.Thread.run(Thread.java:829) ~[?:?]
> 2023-01-12T12:53:03.281-0500 CEF:1 | org.ops4j.pax.web.pax-web-runtime |
> 8.0.6 | ERROR | ID=274 THR=ange controller) CAT=Activator
> MSG=Unable to start Pax Web server: null
> java.lang.NullPointerException: null
> at
> org.eclipse.jetty.util.ssl.SslContextFactory.getKeyManagers(SslContextFactory.java:1249)
> ~[?:?]
> at
> org.eclipse.jetty.util.ssl.SslContextFactory$Server.getKeyManagers(SslContextFactory.java:2364)
> ~[?:?]
> at
> org.eclipse.jetty.util.ssl.SslContextFactory.load(SslContextFactory.java:373)
> ~[?:?]
> at
> org.eclipse.jetty.util.ssl.SslContextFactory.doStart(SslContextFactory.java:244)
> ~[?:?]
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
> ~[?:?]
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
> ~[?:?]
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117)
> ~[?:?]
> at
> org.eclipse.jetty.server.SslConnectionFactory.doStart(SslConnectionFactory.java:97)
> ~[?:?]
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
> ~[?:?]
> at
>
Re: karaf-4.5.x?
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: Unable to start Pax-Web 8.0.6 by using PFX Certificate.
Hi Team,
I have migrated karaf version 4.4.1 and OpenJDK 11 also. Tried to using PFX
file but it was failed due to given below stack trace.
Please can anyone take look at once.
2023-01-12T12:53:03.265-0500 CEF:1 | org.eclipse.jetty.util | 9.4.48.v20220622
| WARN | ID=245 THR=ange controller) CAT=AbstractLifeCycle
MSG=FAILED
Server@21d6680d{FAILED}[9.4.48.v20220622]:
java.lang.NullPointerException
java.lang.NullPointerException: null
at
org.eclipse.jetty.util.ssl.SslContextFactory.getKeyManagers(SslContextFactory.java:1249)
~[?:?]
at
org.eclipse.jetty.util.ssl.SslContextFactory$Server.getKeyManagers(SslContextFactory.java:2364)
~[?:?]
at
org.eclipse.jetty.util.ssl.SslContextFactory.load(SslContextFactory.java:373)
~[?:?]
at
org.eclipse.jetty.util.ssl.SslContextFactory.doStart(SslContextFactory.java:244)
~[?:?]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
~[?:?]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
~[?:?]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117)
~[?:?]
at
org.eclipse.jetty.server.SslConnectionFactory.doStart(SslConnectionFactory.java:97)
~[?:?]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
~[?:?]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
~[?:?]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117)
~[?:?]
at
org.eclipse.jetty.server.AbstractConnector.doStart(AbstractConnector.java:323)
~[?:?]
at
org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:81)
~[?:?]
at
org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:234)
~[?:?]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
~[?:?]
at org.eclipse.jetty.server.Server.doStart(Server.java:401) ~[?:?]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
~[?:?]
at
org.ops4j.pax.web.service.jetty.internal.JettyServerWrapper.start(JettyServerWrapper.java:623)
~[?:?]
at
org.ops4j.pax.web.service.jetty.internal.JettyServerController.start(JettyServerController.java:109)
~[?:?]
at
org.ops4j.pax.web.service.internal.Activator.performConfiguration(Activator.java:551)
~[?:?]
at
org.ops4j.pax.web.service.internal.Activator.updateController(Activator.java:441)
~[?:?]
at
org.ops4j.pax.web.service.internal.Activator.lambda$updateServerControllerFactory$1(Activator.java:347)
~[?:?]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
~[?:?]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
~[?:?]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
~[?:?]
at java.lang.Thread.run(Thread.java:829) ~[?:?]
2023-01-12T12:53:03.281-0500 CEF:1 | org.ops4j.pax.web.pax-web-runtime | 8.0.6
| ERROR | ID=274 THR=ange controller) CAT=Activator
MSG=Unable to start Pax Web server: null
java.lang.NullPointerException: null
at
org.eclipse.jetty.util.ssl.SslContextFactory.getKeyManagers(SslContextFactory.java:1249)
~[?:?]
at
org.eclipse.jetty.util.ssl.SslContextFactory$Server.getKeyManagers(SslContextFactory.java:2364)
~[?:?]
at
org.eclipse.jetty.util.ssl.SslContextFactory.load(SslContextFactory.java:373)
~[?:?]
at
org.eclipse.jetty.util.ssl.SslContextFactory.doStart(SslContextFactory.java:244)
~[?:?]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
~[?:?]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
~[?:?]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117)
~[?:?]
at
org.eclipse.jetty.server.SslConnectionFactory.doStart(SslConnectionFactory.java:97)
~[?:?]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
~[?:?]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
~[?:?]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117)
~[?:?]
at
org.eclipse.jetty.server.AbstractConnector.doStart(AbstractConnector.java:323)
~[?:?]
at
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 Matt, Unfortunately I didn't saw a real answer and no mention in the Camel V4 roadmap... regards, Francois On 12/01/2023 15:51, Matt Pavlovich wrote: Hi François- I recall the discussion about removing the OSGi support from Camel, but I do not see it listed on the ROADMAP to Camel 4 link. Did OSGi header support for camel jars officially get dropped? Seems like such a minor thing to keep around. -Matt On Jan 9, 2023, at 3: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 François- I recall the discussion about removing the OSGi support from Camel, but I do not see it listed on the ROADMAP to Camel 4 link. Did OSGi header support for camel jars officially get dropped? Seems like such a minor thing to keep around. -Matt > On Jan 9, 2023, at 3: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: [VOTE] Apache Karaf OSGi runtime 4.3.9 release
+1 non-binding > On Jan 10, 2023, at 11:41 AM, 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
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 > > > > > > > > > >
