Cannot validate extension in multi-project Gradle build about quarkus

[quarkus-bot]

/cc @glefloch, @quarkusio/devtools

[aloubyansky]

It looks like it can't resolve the deployment project for validation purposes. I am not sure we can do much about it but build extensions completely or disable validateExtension task

[mikethecalamity]

@aloubyansky Could I add something to the json-logging/build.gradle like:

afterEvaluate {
    validateExtension.dependsOn project(':json-logging-deployment').???
}

I just don't know what task from json-logging-deployment that it depends on.

[aloubyansky]

Afaiu, the deployment subproject needs to be a part of the project build, since this task is validating its dependencies.
You need to be careful not to introduce a cyclic dependency, since deployment depends on runtime.
Practically though, I am not sure why you would not want to build them as a "unit".

[mikethecalamity]

I do want to build them as a "unit", but the way builds work for our system requires everything to be able to be built "solo". And I use quotes there because json-logging-deployment can be built as part of json-logging, if there's a way I can add it to the build.gradle. Such that building the json-logging project builds them both. I'm just not sure what I could add in either of their build.gradles to accomplish this.

[aloubyansky]

I think for the validation to work, the deployment subproject has to be included in the build. TBH, I am not sure how you can do that from the runtime subproject, except building the whole "extension" (https://github.com/mikethecalamity/quarkus-test/tree/master/extensions
/subprojects)
Alternatively, validateExtension task could be disabled. Perhaps, we should just move validateExtension to the deployment module but it would still be validating the runtime one.

[mikethecalamity]

I'll disable validateExtension for now. But it does sound reasonable for it to be on the deployment module.