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

Resolution fails when a dependency with Gradle module metadata relies on constraints from a platform dependency #360

Closed
wilkinsona opened this issue Jul 13, 2023 · 0 comments

Comments

@wilkinsona
Copy link
Contributor

This is a regression caused by the fix for #310.

@wilkinsona wilkinsona added this to the 1.1.x milestone Jul 13, 2023
wilkinsona added a commit that referenced this issue Jul 13, 2023
This is a follow-on to cf49bef and adds a test that verifies the
behavior when a dependency has Gradle module metadata and in this
metadata that is a dependency upon a platform.

See gh-360
@wilkinsona wilkinsona changed the title Resolution fails when a dependency relies on dependency management from its parent Resolution fails when a dependency with Gradle module metadata relies on dependency management from a platform dependency Jul 13, 2023
@wilkinsona wilkinsona changed the title Resolution fails when a dependency with Gradle module metadata relies on dependency management from a platform dependency Resolution fails when a dependency with Gradle module metadata relies on constraints from a platform dependency Jul 13, 2023
@wilkinsona wilkinsona modified the milestones: 1.1.x, 1.1.2 Jul 13, 2023
@wilkinsona wilkinsona pinned this issue Jul 14, 2023
@wilkinsona wilkinsona unpinned this issue May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant