You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@kafka.apache.org by fpapon <fp...@apache.org> on 2023/01/09 09:07:23 UTC
[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: [DISCUSS] Apache Karaf subprojects Roadmap
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
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 <st...@gmail.com> 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é <jb...@nanthrax.net>
> 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 <gr...@gmail.com>
> > 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 <fp...@apache.org> 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 <fp...@apache.org> 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
Posted by Steven Huypens <st...@gmail.com>.
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é <jb...@nanthrax.net>
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 <gr...@gmail.com>
> 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 <fp...@apache.org> 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 <fp...@apache.org> 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
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
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 <gr...@gmail.com> 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 <fp...@apache.org> 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 <fp...@apache.org> 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
Posted by Grzegorz Grzybek <gr...@gmail.com>.
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 <fp...@apache.org> 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 <fp...@apache.org> 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
Posted by Francois Papon <fr...@openobject.fr>.
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 <fp...@apache.org> 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 <fp...@apache.org> 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
Posted by Matt Pavlovich <ma...@gmail.com>.
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 <fp...@apache.org> 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 <fp...@apache.org> 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
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
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
<fr...@openobject.fr> 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 <fp...@apache.org> 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 <fp...@apache.org> 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
Posted by Francois Papon <fr...@openobject.fr>.
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 <fp...@apache.org> 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 <fp...@apache.org> 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
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
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 <fp...@apache.org> 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 <fp...@apache.org> 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
Posted by fpapon <fp...@apache.org>.
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 <fp...@apache.org> 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
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
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 <fp...@apache.org> 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
>
Re: [DISCUSS] Apache Karaf subprojects Roadmap
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
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 <fp...@apache.org> 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
>
Re: [DISCUSS] Apache Karaf subprojects Roadmap
Posted by fpapon <fp...@apache.org>.
Ha, yes...sorry for the noise, it's monday morning :)
regards,
François
On 09/01/2023 10:26, Joris Peeters wrote:
> I think that went to users@kafka instead of users@karaf.
>
> On Mon, Jan 9, 2023 at 9:08 AM fpapon <fp...@apache.org> 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