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 < [email protected]> 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 <[email protected]> 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 < >> > [email protected]> wrote: >> > >> >> Kris, >> >> >> >> Are we going to have org.sonataflow too? >> >> >> >> Cheers! >> >> >> >> On Fri, 6 Oct 2023 at 7:38 AM Tibor Zimányi <[email protected]> >> 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 >> >>
