Skip to content

Conversation

pkoenig10
Copy link
Member

@pkoenig10 pkoenig10 commented May 14, 2025

This internal type was renamed in gradle/gradle#29166 and then again in gradle/gradle#29376.

Comment on lines +42 to +46
// This internal exception was renamed in https://github.com/gradle/gradle/pull/29166 and
// https://github.com/gradle/gradle/pull/29376
private static final Set<String> TOOLCHAIN_EXCEPTIONS = Set.of(
"org.gradle.jvm.toolchain.internal.NoToolchainAvailableException",
"org.gradle.jvm.toolchain.internal.install.exceptions.ToolchainProvisioningException");
Copy link
Member Author

Choose a reason for hiding this comment

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

Is there an alternative solution that does not requiring using internal types?

Copy link
Contributor

Choose a reason for hiding this comment

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

Briefly looking, I don't think so. This is definitely the less risky way of checking the exception, although it does mean this feature may break without us knowing this is what the tests in this repo should be checking.

Copy link
Contributor

Choose a reason for hiding this comment

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

Hardcoded test versions strike again - will follow up with fixing that.

@CRogers
Copy link
Contributor

CRogers commented May 14, 2025

👍

@bulldozer-bot bulldozer-bot bot merged commit 1b0857a into develop May 14, 2025
6 checks passed
@bulldozer-bot bulldozer-bot bot deleted the pkoenig/exception branch May 14, 2025 19:05
@autorelease3
Copy link

autorelease3 bot commented May 14, 2025

Released 0.67.0

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.

2 participants