Introduced quarkus-bootstrap-bom

[aloubyansky]

Fixes #12628

This PR also makes sure the proper maven-settings artifact is used to parse the Maven settings file by the bootstrap module during the tests.

[quarkus-bot]

This workflow status is outdated as a new workflow run has been triggered.

Failing Jobs - Building 0076dc5

Status	Name	Step	Test failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
✖	JVM Tests - JDK 11 Windows	Build	Test failures	Logs	Raw logs
✔️	JVM Tests - JDK 16
✖	Native Tests - Data3	Build	⚠️ Check →	Logs	Raw logs

Full information is available in the Build summary check run.

Test Failures

⚙️ JVM Tests - JDK 11 Windows #

📦 extensions/arc/deployment

✖ io.quarkus.arc.test.config.ConfigMappingTest. - More details - Source on GitHub

[famod]

I wonder if some deps should now be removed from the app BOM that are already in the bootstrap BOM, e.g. maven-resolver?

[quarkus-bot]

This workflow status is outdated as a new workflow run has been triggered.

Failing Jobs - Building 7e232cf

Status	Name	Step	Test failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
✖	JVM Tests - JDK 16	Build	Test failures	Logs	Raw logs

Full information is available in the Build summary check run.

Test Failures

⚙️ JVM Tests - JDK 16 #

📦 integration-tests/scala

✖ io.quarkus.scala.maven.it.ScalaRemoteDevModeIT.testThatTheApplicationIsReloadedOnScalaChange line 25 - More details - Source on GitHub

[aloubyansky]

I wonder if some deps should now be removed from the app BOM that are already in the bootstrap BOM, e.g. maven-resolver?

Yes, I'll clean it up. Thanks.

[famod]

LGTM!
TBH, first I didn't really like the addition of yet another BOM, but after having digged myself for while, I now do also think that this is the only way to really enforce everything we need.

I'd just like to point out #9595, which introduced sisu to the app BOM. Maybe this should be revisited/moved as well.

[aloubyansky]

Thanks for reviewing @famod I moved the sisu inject to the bootstrap bom.

[quarkus-bot]

Failing Jobs - Building 0d85188

Status	Name	Step	Test failures	Logs	Raw logs
✖	Native Tests - Data3	Build	⚠️ Check →	Logs	Raw logs

[famod]

@aloubyansky this change causes a build warning (spotted locally);

[WARNING]
[WARNING] Some problems were encountered while building the effective model for io.quarkus:quarkus-bootstrap-bom:pom:999-SNAPSHOT
[WARNING] 'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: io.quarkus:quarkus-bootstrap-core:jar -> duplicate declaration of version ${project.version} @ line 80, column 25
[WARNING] 'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: io.quarkus:quarkus-bootstrap-app-model:jar -> duplicate declaration of version ${project.version} @ line 92, column 25
[WARNING] 'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: io.quarkus:quarkus-bootstrap-maven-resolver:jar -> duplicate declaration of version ${project.version} @ line 97, column 25
[WARNING] 'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: io.quarkus:quarkus-bootstrap-gradle-resolver:jar -> duplicate declaration of version ${project.version} @ line 107, column 25
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]

[aloubyansky]

Sorry about that #18196