Quarkus extension conditional dependencies

[aloubyansky]

Description

It becomes more and more evident that the dependency resolution mechanism is lacking a feature of including certain extra dependencies only in cases when all their required dependencies are satisfied and not including them if at least one of their dependencies isn't found among the project's dependencies.

Given that Quarkus Maven and Gradle plugins use different (build system-specific) dependency resolver implementations, this issue will be split into the following subtasks:

• support for extension conditional dependencies for Maven projects (Conditional extension dependencies support for Maven-based projects #15736)
• support for extension conditional dependencies for Gradle projects (Handle conditional dependency resolution in Gradle #16147)
• documentation on how to use, configure and analyze conditional dependencies

[quarkus-bot]

/cc @MichalMaler, @ebullient, @glefloch, @hmanwani-rh, @inoxx03, @michelle-purcell, @quarkusio/devtools, @sheilamjones, @sunayna15

[maxandersen]

@aloubyansky this issue was done except for the documentation was not marked as done.

I see https://quarkus.io/guides/conditional-extension-dependencies is there.

Thus closing this. If things missing in docs please open separate more dedicated issue.