This issue is to track effort to properly separate the BoMs for Quarkus and Springboot in Drools.

Ideally it should be possible to have a BoM for drools/quarkus projects, a BoM for drools/Springboot projects and a BoM for pure Drools project.

As demontrated by PRs on quarkus upgrade, version of the same libraries are declared/duplicated in multiple boms/poms, making harder to maintain/keep in sync them all over the repositories.

Scope of this ticket is to:

• identify all of them
• group all of them in one single pom.xml inside the "drools" repository and have all of them inherited throughout the codebase, so that such version would be declared only in one single place
• one of the observed pattern is that the version is declared in some pom, and then the library itself is declared in some dependencyManagement tag in children pom - which some how break the concept of dependencyManagement in two different places (the pom where the version is declared as property and the one where it is used in the dependencyManagement) and lead to the duplication - ideally, we should need one single dependencyManagement declaration all over the stack
• enforce clearly separated pom hierarchies between quarkus and springboot frameworks

This comes from suggestions of @gitgabrio and discussions with @mariofusco