Skip to content
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

Make sure super-configuration are used for dependency resolution #19462

Merged
merged 1 commit into from
Aug 18, 2021

Conversation

glefloch
Copy link
Member

For conditional dependency resolution, we create/copy new configuration based on existing configuration (implementation, testImplementation, ...)

When duplicating configuration we are not loading all dependency of the configuration (a configuration can inherit from an other one). This can lead to resolution error due to missing dependency. This make sure load all dependency from the configuration when duplicating it.

close #19386

@quarkus-bot quarkus-bot bot added area/devtools Issues/PR related to maven, gradle, platform and cli tooling/plugins area/gradle Gradle labels Aug 17, 2021
Copy link
Contributor

@gastaldi gastaldi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@glefloch glefloch merged commit 11a3604 into quarkusio:main Aug 18, 2021
@quarkus-bot quarkus-bot bot added this to the 2.2 - main milestone Aug 18, 2021
@glefloch glefloch deleted the fix/19386 branch August 18, 2021 06:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/devtools Issues/PR related to maven, gradle, platform and cli tooling/plugins area/gradle Gradle
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Gradle error finding subproject dependency version
4 participants