Use per-package local Maven repositories for dependency declaration correctness on kie-tools

[tiagobento]

To make sure packages can only consume what they declare as a dependency, leveraging maven.repo.local.tail is essential.

When building (I.e., mvn clean verify), Maven-based packages on kie-tools won't install their resulting JARs to maven.repo.local anymore, but instead to dist/1st-party-m2. This way, the "shared" (a.k.a head) local repository won't contain the artifacts produced by Maven-based packages, making it impossible to access modules that have not been declared as a dependency.

[tiagobento]

I submitted

• kie-issues#1506: Use per-package local Maven repositories for dependency declaration correctness on kie-tools incubator-kie-tools#2635

but it is currently blocked by

• Use ChainedLocalRepositoryManager to support -Dmaven.repo.local.tail quarkusio/quarkus#43352

not being included in a Quarkus release yet.

Hopefully we'll get this on a upcoming 3.15 patch release, so we can upgrade kie-tools to Quarkus 3.15.x and unblock this work.

[tiagobento]

Please see

• NO-ISSUE: Enable Maven's local repo tail mechanism for safer dependency relationship between Maven-based packages incubator-kie-tools#2905

too for the conclusion of this work.