Gradle multi-module project - streamline bean discovery

[huw0]

Description

As outlined in Contexts and Dependency Injection, the bean archive is synthesized from:

• the application classes,
• dependencies that contain a beans.xml descriptor (content is ignored),
• dependencies that contain a Jandex index - META-INF/jandex.idx,
• dependencies referenced by quarkus.index-dependency in application.properties,
• and Quarkus integration code.

All of these are quite clunky in a multi-module gradle project. Options are:

• A load of blank beans.xml files
• Jandex gradle plugin. However this is another thing to manually update to keep in line with the recommended Quarkus Gradle version and the Gradle API changes frequently cause problems
  • kordamp/jandex-gradle-plugin#9
  • kordamp/jandex-gradle-plugin#11
  • kordamp/jandex-gradle-plugin#11 (again with Gradle 7.5)
  • kordamp/jandex-gradle-plugin#21 (discovering that this does not apply to Quarkus - yet)
• Adding to application.properties for every single module

Implementation ideas

• quarkus.index-dependency could support a wildcard for artifactId and/or become optional? Docs imply this is presently mandatory?
• Ideally - modules in the same project would be included in the bean archive as standard and then would be opt-out

[quarkus-bot[bot]]

/cc @glefloch, @quarkusio/devtools