-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot validate extension in multi-project Gradle build #42054
Comments
/cc @glefloch, @quarkusio/devtools |
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 |
@aloubyansky Could I add something to the afterEvaluate {
validateExtension.dependsOn project(':json-logging-deployment').???
} I just don't know what task from |
Afaiu, the deployment subproject needs to be a part of the project build, since this task is validating its dependencies. |
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 |
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 |
I'll disable |
Describe the bug
I created a custom extension in my multi-project Gradle build. But I cannot build the extension project solo (
gradlew -p <project> <subproject>:build
). But the build succeeds when I build everything (gradlew -p <project> build
).Expected behavior
Successful build
Actual behavior
How to Reproduce?
Reproducer:
./gradlew -p extensions json-logging:build
Output of
uname -a
orver
No response
Output of
java -version
JDK 17
Quarkus version or git rev
Quarkus 3.12.3
Build tool (ie. output of
mvnw --version
orgradlew --version
)Gradle 8.9
Additional information
No response
The text was updated successfully, but these errors were encountered: