Re: [PROPOSAL] Karaf 5

[Romain Manni-Bucau]

Hi

think it makes sense to keep another repo.
However it probably does not to have the version in it (when it will be v6
why would the repo be named v5 ;)).
Since it is a new project, wider than karaf4, I guess it should be renamed
(karaf-xxx) instead of merged to an unrelated project, no?

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



Le lun. 7 févr. 2022 à 08:31, Grzegorz Grzybek  a
écrit :

> Hello
>
> Great to hear about Karaf5 progress. Do I understand correctly that you
> think about `K5` branch in apache/karaf repo? If there's no common history,
> why simply not https://github.com/apache/karaf5 ?
>
> regards
> Grzegorz Grzybek
>
> pon., 7 lut 2022 o 08:25 Francois Papon 
> napisał(a):
>
> > Of course ;)
> >
> > On 07/02/2022 08:22, JB Onofré wrote:
> > > Let’s wait for others feedback on the mailing list.
> > >
> > >> Le 7 févr. 2022 à 08:08, Francois Papon  >
> > a écrit :
> > >>
> > >> I can manage the creation of the branch and move the code source.
> > >>
> > >> regards,
> > >>
> > >> François
> > >>
> > >>> On 07/02/2022 08:05, Francois Papon wrote:
> > >>> +1, we can use a dedicated branch :)
> > >>>
> > >>> regards,
> > >>>
> > >>> Francois
> > >>>
> >  On 07/02/2022 08:02, Jean-Baptiste Onofre wrote:
> >  Hi,
> > 
> >  It sounds good to me.
> > 
> >  The K5 repo is currently on my GitHub:
> > 
> >  https://github.com/jbonofre/karaf5
> > 
> >  I propose:
> > 
> >  1. To keep main for karaf-4.4.x for now
> >  2. Fix K4 like assembly on K5 (just have to push some new services)
> >  3. Push Karaf 5 on K5 branch
> >  4. Improve documentation on K5 branch to show what’s a service, and
> > so, allow anyone to contribute service/distribution
> > 
> >  ETA: end of this week if no objection.
> > 
> >  Regards
> >  JB
> > 
> > 
> > > Le 7 févr. 2022 à 07:56, Francois Papon <
> > francois.pa...@openobject.fr> a écrit :
> > >
> > > Hi,
> > >
> > > As we have some users that asking questions about Karaf 5 the next
> > Karaf generation, I think it would be nice to move the current repo to
> > master.
> > >
> > > It could be a good booster if we want to move forward on this for a
> > first RC.
> > >
> > > Thoughts?
> > >
> > > Regards,
> > >
> > > François
> > >
> >
>

Re: [PROPOSAL] Karaf 5

[JB Onofré]

Yes the first plan is karaf-5.x branch on karaf repo (not a new repo). 
I think it’s better in term of visibility and roadmap. 

Regards 
JB

> Le 7 févr. 2022 à 08:31, Grzegorz Grzybek  a écrit :
> 
> Hello
> 
> Great to hear about Karaf5 progress. Do I understand correctly that you
> think about `K5` branch in apache/karaf repo? If there's no common history,
> why simply not https://github.com/apache/karaf5 ?
> 
> regards
> Grzegorz Grzybek
> 
> pon., 7 lut 2022 o 08:25 Francois Papon 
> napisał(a):
> 
>> Of course ;)
>> 
>>> On 07/02/2022 08:22, JB Onofré wrote:
>>> Let’s wait for others feedback on the mailing list.
>>> 
 Le 7 févr. 2022 à 08:08, Francois Papon 
>> a écrit :
 
 I can manage the creation of the branch and move the code source.
 
 regards,
 
 François
 
> On 07/02/2022 08:05, Francois Papon wrote:
> +1, we can use a dedicated branch :)
> 
> regards,
> 
> Francois
> 
>> On 07/02/2022 08:02, Jean-Baptiste Onofre wrote:
>> Hi,
>> 
>> It sounds good to me.
>> 
>> The K5 repo is currently on my GitHub:
>> 
>> https://github.com/jbonofre/karaf5
>> 
>> I propose:
>> 
>> 1. To keep main for karaf-4.4.x for now
>> 2. Fix K4 like assembly on K5 (just have to push some new services)
>> 3. Push Karaf 5 on K5 branch
>> 4. Improve documentation on K5 branch to show what’s a service, and
>> so, allow anyone to contribute service/distribution
>> 
>> ETA: end of this week if no objection.
>> 
>> Regards
>> JB
>> 
>> 
>>> Le 7 févr. 2022 à 07:56, Francois Papon <
>> francois.pa...@openobject.fr> a écrit :
>>> 
>>> Hi,
>>> 
>>> As we have some users that asking questions about Karaf 5 the next
>> Karaf generation, I think it would be nice to move the current repo to
>> master.
>>> 
>>> It could be a good booster if we want to move forward on this for a
>> first RC.
>>> 
>>> Thoughts?
>>> 
>>> Regards,
>>> 
>>> François
>>> 
>> 

Re: [PROPOSAL] Karaf 5

[Grzegorz Grzybek]

Hello

Great to hear about Karaf5 progress. Do I understand correctly that you
think about `K5` branch in apache/karaf repo? If there's no common history,
why simply not https://github.com/apache/karaf5 ?

regards
Grzegorz Grzybek

pon., 7 lut 2022 o 08:25 Francois Papon 
napisał(a):

> Of course ;)
>
> On 07/02/2022 08:22, JB Onofré wrote:
> > Let’s wait for others feedback on the mailing list.
> >
> >> Le 7 févr. 2022 à 08:08, Francois Papon 
> a écrit :
> >>
> >> I can manage the creation of the branch and move the code source.
> >>
> >> regards,
> >>
> >> François
> >>
> >>> On 07/02/2022 08:05, Francois Papon wrote:
> >>> +1, we can use a dedicated branch :)
> >>>
> >>> regards,
> >>>
> >>> Francois
> >>>
>  On 07/02/2022 08:02, Jean-Baptiste Onofre wrote:
>  Hi,
> 
>  It sounds good to me.
> 
>  The K5 repo is currently on my GitHub:
> 
>  https://github.com/jbonofre/karaf5
> 
>  I propose:
> 
>  1. To keep main for karaf-4.4.x for now
>  2. Fix K4 like assembly on K5 (just have to push some new services)
>  3. Push Karaf 5 on K5 branch
>  4. Improve documentation on K5 branch to show what’s a service, and
> so, allow anyone to contribute service/distribution
> 
>  ETA: end of this week if no objection.
> 
>  Regards
>  JB
> 
> 
> > Le 7 févr. 2022 à 07:56, Francois Papon <
> francois.pa...@openobject.fr> a écrit :
> >
> > Hi,
> >
> > As we have some users that asking questions about Karaf 5 the next
> Karaf generation, I think it would be nice to move the current repo to
> master.
> >
> > It could be a good booster if we want to move forward on this for a
> first RC.
> >
> > Thoughts?
> >
> > Regards,
> >
> > François
> >
>

Re: [PROPOSAL] Karaf 5

[Francois Papon]

Of course ;)

On 07/02/2022 08:22, JB Onofré wrote:

Let’s wait for others feedback on the mailing list.


Le 7 févr. 2022 à 08:08, Francois Papon  a écrit :

I can manage the creation of the branch and move the code source.

regards,

François


On 07/02/2022 08:05, Francois Papon wrote:
+1, we can use a dedicated branch :)

regards,

Francois


On 07/02/2022 08:02, Jean-Baptiste Onofre wrote:
Hi,

It sounds good to me.

The K5 repo is currently on my GitHub:

https://github.com/jbonofre/karaf5

I propose:

1. To keep main for karaf-4.4.x for now
2. Fix K4 like assembly on K5 (just have to push some new services)
3. Push Karaf 5 on K5 branch
4. Improve documentation on K5 branch to show what’s a service, and so, allow 
anyone to contribute service/distribution

ETA: end of this week if no objection.

Regards
JB



Le 7 févr. 2022 à 07:56, Francois Papon  a écrit :

Hi,

As we have some users that asking questions about Karaf 5 the next Karaf 
generation, I think it would be nice to move the current repo to master.

It could be a good booster if we want to move forward on this for a first RC.

Thoughts?

Regards,

François

Re: [PROPOSAL] Karaf 5

[JB Onofré]

Let’s wait for others feedback on the mailing list. 

> Le 7 févr. 2022 à 08:08, Francois Papon  a 
> écrit :
> 
> I can manage the creation of the branch and move the code source.
> 
> regards,
> 
> François
> 
>> On 07/02/2022 08:05, Francois Papon wrote:
>> +1, we can use a dedicated branch :)
>> 
>> regards,
>> 
>> Francois
>> 
>>> On 07/02/2022 08:02, Jean-Baptiste Onofre wrote:
>>> Hi,
>>> 
>>> It sounds good to me.
>>> 
>>> The K5 repo is currently on my GitHub:
>>> 
>>> https://github.com/jbonofre/karaf5
>>> 
>>> I propose:
>>> 
>>> 1. To keep main for karaf-4.4.x for now
>>> 2. Fix K4 like assembly on K5 (just have to push some new services)
>>> 3. Push Karaf 5 on K5 branch
>>> 4. Improve documentation on K5 branch to show what’s a service, and so, 
>>> allow anyone to contribute service/distribution
>>> 
>>> ETA: end of this week if no objection.
>>> 
>>> Regards
>>> JB
>>> 
>>> 
 Le 7 févr. 2022 à 07:56, Francois Papon  a 
 écrit :
 
 Hi,
 
 As we have some users that asking questions about Karaf 5 the next Karaf 
 generation, I think it would be nice to move the current repo to master.
 
 It could be a good booster if we want to move forward on this for a first 
 RC.
 
 Thoughts?
 
 Regards,
 
 François
 

Karaf 5 shell and native

[Bernd Eckenfels]

Hello,

I wonder are there any plans for native image and tree shaking for karaf5?

 Especially I think we need a shell framework (like quarkus/picocli) which 
allows a fast stand-alone cli. At least if karaf plans to play in this space. I 
like the OSGi console command abstraction, so it would be a good candidate if 
one can proceed to write (Developer and ops) commands this way and then compile 
it.

This could even abstract away some of the more arcane to use maven steps 
(archetype) and add new things like development server or even client.sh.

Gruss
Bernd


--
http://bernd.eckenfels.net

Re: [PROPOSAL] Karaf 5

[Francois Papon]

I can manage the creation of the branch and move the code source.

regards,

François

On 07/02/2022 08:05, Francois Papon wrote:

+1, we can use a dedicated branch :)

regards,

Francois

On 07/02/2022 08:02, Jean-Baptiste Onofre wrote:

Hi,

It sounds good to me.

The K5 repo is currently on my GitHub:

https://github.com/jbonofre/karaf5

I propose:

1. To keep main for karaf-4.4.x for now
2. Fix K4 like assembly on K5 (just have to push some new services)
3. Push Karaf 5 on K5 branch
4. Improve documentation on K5 branch to show what’s a service, and 
so, allow anyone to contribute service/distribution


ETA: end of this week if no objection.

Regards
JB


Le 7 févr. 2022 à 07:56, Francois Papon 
 a écrit :


Hi,

As we have some users that asking questions about Karaf 5 the next 
Karaf generation, I think it would be nice to move the current repo 
to master.


It could be a good booster if we want to move forward on this for a 
first RC.


Thoughts?

Regards,

François

Re: [PROPOSAL] Karaf 5

[Francois Papon]

+1, we can use a dedicated branch :)

regards,

Francois

On 07/02/2022 08:02, Jean-Baptiste Onofre wrote:

Hi,

It sounds good to me.

The K5 repo is currently on my GitHub:

https://github.com/jbonofre/karaf5

I propose:

1. To keep main for karaf-4.4.x for now
2. Fix K4 like assembly on K5 (just have to push some new services)
3. Push Karaf 5 on K5 branch
4. Improve documentation on K5 branch to show what’s a service, and so, allow 
anyone to contribute service/distribution

ETA: end of this week if no objection.

Regards
JB



Le 7 févr. 2022 à 07:56, Francois Papon  a écrit :

Hi,

As we have some users that asking questions about Karaf 5 the next Karaf 
generation, I think it would be nice to move the current repo to master.

It could be a good booster if we want to move forward on this for a first RC.

Thoughts?

Regards,

François

Re: [PROPOSAL] Karaf 5

[Jean-Baptiste Onofre]

Hi,

It sounds good to me.

The K5 repo is currently on my GitHub:

https://github.com/jbonofre/karaf5

I propose:

1. To keep main for karaf-4.4.x for now
2. Fix K4 like assembly on K5 (just have to push some new services)
3. Push Karaf 5 on K5 branch
4. Improve documentation on K5 branch to show what’s a service, and so, allow 
anyone to contribute service/distribution

ETA: end of this week if no objection.

Regards
JB


> Le 7 févr. 2022 à 07:56, Francois Papon  a 
> écrit :
> 
> Hi,
> 
> As we have some users that asking questions about Karaf 5 the next Karaf 
> generation, I think it would be nice to move the current repo to master.
> 
> It could be a good booster if we want to move forward on this for a first RC.
> 
> Thoughts?
> 
> Regards,
> 
> François
> 

[PROPOSAL] Karaf 5

[Francois Papon]

Hi,

As we have some users that asking questions about Karaf 5 the next Karaf 
generation, I think it would be nice to move the current repo to master.


It could be a good booster if we want to move forward on this for a 
first RC.


Thoughts?

Regards,

François