You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kie.apache.org by Tibor Zimányi <tz...@apache.org> on 2023/10/06 10:38:25 UTC
[DISCUSS][build] A list of groupIds we have
Hi everyone,
I want to create a ticket for us to get access to Apache Nexus, so we can
start to deploy snapshot and other artifacts there. For that I need a list
of groupIds we use in our Maven artifacts. I am aware of these:
org.drools
org.kie
org.kie.kogito
Are there any other groupIds that I should mention in the ticket please?
Best regards,
Tibor
Re: [DISCUSS][build] A list of groupIds we have
Posted by Tibor Zimányi <tz...@apache.org>.
Hi everyone,
thank you for your input. Based on it I created the ticket to get access to
Apache Nexus here: https://issues.apache.org/jira/browse/INFRA-25077
I will let you know when there are updates.
Best regards,
Tibor
On Mon, Oct 9, 2023 at 2:57 PM Enrique Gonzalez Martinez <
elguardian@gmail.com> wrote:
> My guess we are not talking about the namespace rather than projects/brands
> Regarding jbpm at some point we will have to strip it from the runtimes.
> This had some prior discussion and agreed to hold the decision till we move
> to apache.
>
> El lun, 9 oct 2023, 14:24, Francisco Javier Tirado Sarti <
> ftirados@redhat.com> escribió:
>
> > My previous message has three key missing words ;)
> > We still have dependencies whose package name is under org.jbpm within
> > kogito (as the one I linked)
> > So, as Kris says org.jbpm is not required as dependency right now, but it
> > looks like it might be handy in the future, specially for dependencies
> that
> > are strictly bpmn ones, as jbpm-bpmn2 (jbpm-flow is both used by bpmn and
> > SWF)
> >
> >
> > On Mon, Oct 9, 2023 at 1:03 PM Francisco Javier Tirado Sarti <
> > ftirados@redhat.com> wrote:
> >
> > > Hi Marek,
> > >
> > > We still have dependencies under org.jbpm within kogito.
> > > For example, see
> > >
> >
> https://github.com/kiegroup/kogito-runtimes/blob/main/jbpm/jbpm-flow/pom.xml
> > >
> > > On Sat, Oct 7, 2023 at 1:21 PM Marek Novotny <mn...@redhat.com>
> > wrote:
> > >
> > >> wrt org.jbpm is that actually part of the transferred repositories? I
> > >> mean if the repository is not transferred there won't be any usage of
> > >> that groupId or Am I missing something?
> > >>
> > >> Dne 10/6/23 v 15:34 Kris Verlaenen napsal(a):
> > >> > Yes, I would add org.sonataflow, org.jbpm, org.optaplanner.
> > >> >
> > >> > Thx,
> > >> > Kris
> > >> >
> > >> >
> > >> > On Fri, Oct 6, 2023 at 1:53 PM ricardo zanini fernandes <
> > >> > ricardozanini@gmail.com> wrote:
> > >> >
> > >> >> Kris,
> > >> >>
> > >> >> Are we going to have org.sonataflow too?
> > >> >>
> > >> >> Cheers!
> > >> >>
> > >> >> On Fri, 6 Oct 2023 at 7:38 AM Tibor Zimányi <tz...@apache.org>
> > >> wrote:
> > >> >>
> > >> >>> Hi everyone,
> > >> >>>
> > >> >>> I want to create a ticket for us to get access to Apache Nexus, so
> > we
> > >> can
> > >> >>> start to deploy snapshot and other artifacts there. For that I
> need
> > a
> > >> >> list
> > >> >>> of groupIds we use in our Maven artifacts. I am aware of these:
> > >> >>> org.drools
> > >> >>> org.kie
> > >> >>> org.kie.kogito
> > >> >>>
> > >> >>> Are there any other groupIds that I should mention in the ticket
> > >> please?
> > >> >>>
> > >> >>> Best regards,
> > >> >>> Tibor
> > >> >>>
> > >> --
> > >> Marek Novotny
> > >> --
> > >>
> > >> RedHat JBoss Middleware
> > >>
> > >> Red Hat Czech s.r.o.
> > >> Purkynova 111
> > >> 612 45 Brno
> > >>
> > >>
> >
>
Re: [DISCUSS][build] A list of groupIds we have
Posted by Enrique Gonzalez Martinez <el...@gmail.com>.
My guess we are not talking about the namespace rather than projects/brands
Regarding jbpm at some point we will have to strip it from the runtimes.
This had some prior discussion and agreed to hold the decision till we move
to apache.
El lun, 9 oct 2023, 14:24, Francisco Javier Tirado Sarti <
ftirados@redhat.com> escribió:
> My previous message has three key missing words ;)
> We still have dependencies whose package name is under org.jbpm within
> kogito (as the one I linked)
> So, as Kris says org.jbpm is not required as dependency right now, but it
> looks like it might be handy in the future, specially for dependencies that
> are strictly bpmn ones, as jbpm-bpmn2 (jbpm-flow is both used by bpmn and
> SWF)
>
>
> On Mon, Oct 9, 2023 at 1:03 PM Francisco Javier Tirado Sarti <
> ftirados@redhat.com> wrote:
>
> > Hi Marek,
> >
> > We still have dependencies under org.jbpm within kogito.
> > For example, see
> >
> https://github.com/kiegroup/kogito-runtimes/blob/main/jbpm/jbpm-flow/pom.xml
> >
> > On Sat, Oct 7, 2023 at 1:21 PM Marek Novotny <mn...@redhat.com>
> wrote:
> >
> >> wrt org.jbpm is that actually part of the transferred repositories? I
> >> mean if the repository is not transferred there won't be any usage of
> >> that groupId or Am I missing something?
> >>
> >> Dne 10/6/23 v 15:34 Kris Verlaenen napsal(a):
> >> > Yes, I would add org.sonataflow, org.jbpm, org.optaplanner.
> >> >
> >> > Thx,
> >> > Kris
> >> >
> >> >
> >> > On Fri, Oct 6, 2023 at 1:53 PM ricardo zanini fernandes <
> >> > ricardozanini@gmail.com> wrote:
> >> >
> >> >> Kris,
> >> >>
> >> >> Are we going to have org.sonataflow too?
> >> >>
> >> >> Cheers!
> >> >>
> >> >> On Fri, 6 Oct 2023 at 7:38 AM Tibor Zimányi <tz...@apache.org>
> >> wrote:
> >> >>
> >> >>> Hi everyone,
> >> >>>
> >> >>> I want to create a ticket for us to get access to Apache Nexus, so
> we
> >> can
> >> >>> start to deploy snapshot and other artifacts there. For that I need
> a
> >> >> list
> >> >>> of groupIds we use in our Maven artifacts. I am aware of these:
> >> >>> org.drools
> >> >>> org.kie
> >> >>> org.kie.kogito
> >> >>>
> >> >>> Are there any other groupIds that I should mention in the ticket
> >> please?
> >> >>>
> >> >>> Best regards,
> >> >>> Tibor
> >> >>>
> >> --
> >> Marek Novotny
> >> --
> >>
> >> RedHat JBoss Middleware
> >>
> >> Red Hat Czech s.r.o.
> >> Purkynova 111
> >> 612 45 Brno
> >>
> >>
>
Re: [DISCUSS][build] A list of groupIds we have
Posted by Francisco Javier Tirado Sarti <ft...@redhat.com>.
My previous message has three key missing words ;)
We still have dependencies whose package name is under org.jbpm within
kogito (as the one I linked)
So, as Kris says org.jbpm is not required as dependency right now, but it
looks like it might be handy in the future, specially for dependencies that
are strictly bpmn ones, as jbpm-bpmn2 (jbpm-flow is both used by bpmn and
SWF)
On Mon, Oct 9, 2023 at 1:03 PM Francisco Javier Tirado Sarti <
ftirados@redhat.com> wrote:
> Hi Marek,
>
> We still have dependencies under org.jbpm within kogito.
> For example, see
> https://github.com/kiegroup/kogito-runtimes/blob/main/jbpm/jbpm-flow/pom.xml
>
> On Sat, Oct 7, 2023 at 1:21 PM Marek Novotny <mn...@redhat.com> wrote:
>
>> wrt org.jbpm is that actually part of the transferred repositories? I
>> mean if the repository is not transferred there won't be any usage of
>> that groupId or Am I missing something?
>>
>> Dne 10/6/23 v 15:34 Kris Verlaenen napsal(a):
>> > Yes, I would add org.sonataflow, org.jbpm, org.optaplanner.
>> >
>> > Thx,
>> > Kris
>> >
>> >
>> > On Fri, Oct 6, 2023 at 1:53 PM ricardo zanini fernandes <
>> > ricardozanini@gmail.com> wrote:
>> >
>> >> Kris,
>> >>
>> >> Are we going to have org.sonataflow too?
>> >>
>> >> Cheers!
>> >>
>> >> On Fri, 6 Oct 2023 at 7:38 AM Tibor Zimányi <tz...@apache.org>
>> wrote:
>> >>
>> >>> Hi everyone,
>> >>>
>> >>> I want to create a ticket for us to get access to Apache Nexus, so we
>> can
>> >>> start to deploy snapshot and other artifacts there. For that I need a
>> >> list
>> >>> of groupIds we use in our Maven artifacts. I am aware of these:
>> >>> org.drools
>> >>> org.kie
>> >>> org.kie.kogito
>> >>>
>> >>> Are there any other groupIds that I should mention in the ticket
>> please?
>> >>>
>> >>> Best regards,
>> >>> Tibor
>> >>>
>> --
>> Marek Novotny
>> --
>>
>> RedHat JBoss Middleware
>>
>> Red Hat Czech s.r.o.
>> Purkynova 111
>> 612 45 Brno
>>
>>
Re: [DISCUSS][build] A list of groupIds we have
Posted by Francisco Javier Tirado Sarti <ft...@redhat.com>.
Hi Marek,
We still have dependencies under org.jbpm within kogito.
For example, see
https://github.com/kiegroup/kogito-runtimes/blob/main/jbpm/jbpm-flow/pom.xml
On Sat, Oct 7, 2023 at 1:21 PM Marek Novotny <mn...@redhat.com> wrote:
> wrt org.jbpm is that actually part of the transferred repositories? I
> mean if the repository is not transferred there won't be any usage of
> that groupId or Am I missing something?
>
> Dne 10/6/23 v 15:34 Kris Verlaenen napsal(a):
> > Yes, I would add org.sonataflow, org.jbpm, org.optaplanner.
> >
> > Thx,
> > Kris
> >
> >
> > On Fri, Oct 6, 2023 at 1:53 PM ricardo zanini fernandes <
> > ricardozanini@gmail.com> wrote:
> >
> >> Kris,
> >>
> >> Are we going to have org.sonataflow too?
> >>
> >> Cheers!
> >>
> >> On Fri, 6 Oct 2023 at 7:38 AM Tibor Zimányi <tz...@apache.org>
> wrote:
> >>
> >>> Hi everyone,
> >>>
> >>> I want to create a ticket for us to get access to Apache Nexus, so we
> can
> >>> start to deploy snapshot and other artifacts there. For that I need a
> >> list
> >>> of groupIds we use in our Maven artifacts. I am aware of these:
> >>> org.drools
> >>> org.kie
> >>> org.kie.kogito
> >>>
> >>> Are there any other groupIds that I should mention in the ticket
> please?
> >>>
> >>> Best regards,
> >>> Tibor
> >>>
> --
> Marek Novotny
> --
>
> RedHat JBoss Middleware
>
> Red Hat Czech s.r.o.
> Purkynova 111
> 612 45 Brno
>
>
Re: [DISCUSS][build] A list of groupIds we have
Posted by Kris Verlaenen <kr...@gmail.com>.
We want to start using org.jbpm again in the near future.
Thx,
Kris
On Sat, Oct 7, 2023 at 1:20 PM Marek Novotny <mn...@redhat.com> wrote:
> wrt org.jbpm is that actually part of the transferred repositories? I
> mean if the repository is not transferred there won't be any usage of
> that groupId or Am I missing something?
>
> Dne 10/6/23 v 15:34 Kris Verlaenen napsal(a):
> > Yes, I would add org.sonataflow, org.jbpm, org.optaplanner.
> >
> > Thx,
> > Kris
> >
> >
> > On Fri, Oct 6, 2023 at 1:53 PM ricardo zanini fernandes <
> > ricardozanini@gmail.com> wrote:
> >
> >> Kris,
> >>
> >> Are we going to have org.sonataflow too?
> >>
> >> Cheers!
> >>
> >> On Fri, 6 Oct 2023 at 7:38 AM Tibor Zimányi <tz...@apache.org>
> wrote:
> >>
> >>> Hi everyone,
> >>>
> >>> I want to create a ticket for us to get access to Apache Nexus, so we
> can
> >>> start to deploy snapshot and other artifacts there. For that I need a
> >> list
> >>> of groupIds we use in our Maven artifacts. I am aware of these:
> >>> org.drools
> >>> org.kie
> >>> org.kie.kogito
> >>>
> >>> Are there any other groupIds that I should mention in the ticket
> please?
> >>>
> >>> Best regards,
> >>> Tibor
> >>>
> --
> Marek Novotny
> --
>
> RedHat JBoss Middleware
>
> Red Hat Czech s.r.o.
> Purkynova 111
> 612 45 Brno
>
>
Re: [DISCUSS][build] A list of groupIds we have
Posted by Marek Novotny <mn...@redhat.com>.
wrt org.jbpm is that actually part of the transferred repositories? I
mean if the repository is not transferred there won't be any usage of
that groupId or Am I missing something?
Dne 10/6/23 v 15:34 Kris Verlaenen napsal(a):
> Yes, I would add org.sonataflow, org.jbpm, org.optaplanner.
>
> Thx,
> Kris
>
>
> On Fri, Oct 6, 2023 at 1:53 PM ricardo zanini fernandes <
> ricardozanini@gmail.com> wrote:
>
>> Kris,
>>
>> Are we going to have org.sonataflow too?
>>
>> Cheers!
>>
>> On Fri, 6 Oct 2023 at 7:38 AM Tibor Zimányi <tz...@apache.org> wrote:
>>
>>> Hi everyone,
>>>
>>> I want to create a ticket for us to get access to Apache Nexus, so we can
>>> start to deploy snapshot and other artifacts there. For that I need a
>> list
>>> of groupIds we use in our Maven artifacts. I am aware of these:
>>> org.drools
>>> org.kie
>>> org.kie.kogito
>>>
>>> Are there any other groupIds that I should mention in the ticket please?
>>>
>>> Best regards,
>>> Tibor
>>>
--
Marek Novotny
--
RedHat JBoss Middleware
Red Hat Czech s.r.o.
Purkynova 111
612 45 Brno
Re: [DISCUSS][build] A list of groupIds we have
Posted by Kris Verlaenen <kr...@gmail.com>.
Yes, I would add org.sonataflow, org.jbpm, org.optaplanner.
Thx,
Kris
On Fri, Oct 6, 2023 at 1:53 PM ricardo zanini fernandes <
ricardozanini@gmail.com> wrote:
> Kris,
>
> Are we going to have org.sonataflow too?
>
> Cheers!
>
> On Fri, 6 Oct 2023 at 7:38 AM Tibor Zimányi <tz...@apache.org> wrote:
>
> > Hi everyone,
> >
> > I want to create a ticket for us to get access to Apache Nexus, so we can
> > start to deploy snapshot and other artifacts there. For that I need a
> list
> > of groupIds we use in our Maven artifacts. I am aware of these:
> > org.drools
> > org.kie
> > org.kie.kogito
> >
> > Are there any other groupIds that I should mention in the ticket please?
> >
> > Best regards,
> > Tibor
> >
>
Re: [DISCUSS][build] A list of groupIds we have
Posted by ricardo zanini fernandes <ri...@gmail.com>.
Kris,
Are we going to have org.sonataflow too?
Cheers!
On Fri, 6 Oct 2023 at 7:38 AM Tibor Zimányi <tz...@apache.org> wrote:
> Hi everyone,
>
> I want to create a ticket for us to get access to Apache Nexus, so we can
> start to deploy snapshot and other artifacts there. For that I need a list
> of groupIds we use in our Maven artifacts. I am aware of these:
> org.drools
> org.kie
> org.kie.kogito
>
> Are there any other groupIds that I should mention in the ticket please?
>
> Best regards,
> Tibor
>