Extend CurateOutcomeBuildItem's AppModel to list all present extensions

[knutwannheden]

Description

I would like to implement an extension which verifies the setup of an application. One part of this verification is to make sure that certain extensions are present or not present. Currently there is no such mechanism offered by Quarkus. There are build items to access the list of capabilities and features, but not for extensions.

Implementation ideas

I propose to add a multi build item for the list of extensions present in the build. This build item would somehow be provided by Quarkus and extensions would not be expected to explicitly produce corresponding build items, only consume it.

[aloubyansky]

I would suggest adding this information to the AppModel instead provided by the CurateOutcomeBuildItem.

[knutwannheden]

I would suggest adding this information to the AppModel instead provided by the CurateOutcomeBuildItem.

That sounds like a good idea. That way there is no confusion regarding a "read-only" build item.

[gsmet]

~~ sorry about the noise ~~

[knutwannheden]

@aloubyansky Can you provide me with some hints on how to implement this? I've tried to understand the code and my guess would have been that I need to extend BootstrapAppModelResolver#doResolveModel() to collect all the extensions using the DeploymentInjectingDependencyVisitor and then pass them to the AppModel.Builder. To achieve this I would probably have extended DeploymentInjectingDependencyVisitor#visitExtensionDependency() to also collect all extDep.info.runtimeArtifact elements.

[aloubyansky]

Pretty much. The DeploymentInjectingDependencyVisitor can add the extension dependencies to the AppModel.Builder directly.

[knutwannheden]

Thanks. I will set up my local Quarkus workspace and try to work on this.

[aloubyansky]

There is also the Gradle side of it, which should be added to the QuarkusModelBuilder. FYI @glefloch