Hi Tibor, Paolo,
my personal view is that the quarkus/springboot boms should be placed
inside kogito-runtimes repository itself, and everything quarkus-related
should be moved from drools-repo to kogito-runtimes.
One of the goals IMO is to completely "clean-up" drools repository from any
framework-related dependency, and move the framework integration inside
kogito-runtimes.
Does this make sense ?

Il giorno mar 29 lug 2025 alle ore 11:06 Tibor Zimányi <tzima...@apache.org>
ha scritto:

> Hi Paolo,
>
> thank you for this initiative. It is really needed, however I think it
> needs to be done on the whole KIE level, not just Drools level. The same
> situation is in kogito-runtimes repository. Therefore I think we need a
> global KIE bom and then global Quarkus bom and global Spring Boot bom.
>
> What do you think, please?
>
> Best regards,
> Tibor
>
>
> Dňa ut 29. 7. 2025, 10:54 Paolo Bizzarri <pibi...@gmail.com> napísal(a):
>
> > Hi,
> >
> > this discussion comes after the concerns expressed by Gabriele in this
> > comment on this PR.
> >
> >
> >
> https://github.com/apache/incubator-kie-drools/pull/6352#issuecomment-2911439196
> >
> > I want to address Gabriele's main points:
> >
> > - keep Drools as much as possible separated from frameworks like Quarkus
> > and Springboot
> > - provide separate BOMs for Quarkus Extension and Springboot Extension.
> >
> > The idea is to have three BOMs - one for simple Drools projects, one for
> > projects that use Droos + Quarkus and one for projects that use Drools +
> > SpringBoot.
> >
> > In this way if a project needs just Drools it could use only the Drools
> > BOM, while a project that wants to use also Quarkus would have to use the
> > Drools + Quarkus BOM.
> >
> > This is a breaking change however - projects that want to use Drools +
> > Quarkus will have to use a different BOM. We can address this in the
> > release notes.
> >
> > I expect the complexity of this change to be minimal, and I am going to
> > take care of it.
> >
> > Let me know your opinion.
> >
> > Regards
> >
> > P.
> >
>

Reply via email to