Skip to content

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

Closed
octylFractal wants to merge 1 commit into
spring-gradle-plugins:mainfrom
octylFractal:fix/explicitly-check-module-component-id
Closed

ExclusionResolver makes assumptions that won't hold true with Gradle 9#394
octylFractal wants to merge 1 commit into
spring-gradle-plugins:mainfrom
octylFractal:fix/explicitly-check-module-component-id

Conversation

@octylFractal

Copy link
Copy Markdown
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
Copy Markdown

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
Copy Markdown
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.

4 participants