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

ExclusionResolver makes assumptions that won't hold true with Gradle 9 #394

Conversation

octylFractal
Copy link
Contributor

This fixes a future issue with an upcoming Gradle feature gradle/gradle#30320, where there would be a new non-module-id resulting in a bug similar to
gradle/gradle#30239.

This also fixes a minor bug as it is technically possible for getModuleVersion to return null.

This fixes a future issue with an upcoming Gradle feature
gradle/gradle#30320, where there would be a
new non-module-id resulting in a bug similar to
gradle/gradle#30239.

This also fixes a minor bug as it is technically possible
for getModuleVersion to return null.
@jvandort
Copy link

LGTM

@wilkinsona wilkinsona changed the title Check for ModuleComponentIdentifier explicitly ExclusionResolver makes assumptions that won't hold true with Gradle 9 Sep 2, 2024
@wilkinsona wilkinsona added this to the 1.1.7 milestone Sep 2, 2024
wilkinsona pushed a commit that referenced this pull request Sep 2, 2024
This fixes a future issue with an upcoming Gradle feature
gradle/gradle#30320, where there would be a
new non-module-id resulting in a bug similar to
gradle/gradle#30239.

This also fixes a minor bug as it is technically possible
for getModuleVersion to return null.

See gh-394
@wilkinsona wilkinsona closed this in 0d1b43d Sep 2, 2024
@wilkinsona
Copy link
Contributor

Thanks very much, @octylFractal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants