Gradle 8: Use dynamic proxy for JavaInstallationMetadata

[CRogers]

Before this PR

When used on Gradle 8, running compileJava or related java tasks leads to an error:

Execution failed for task ':<project>:compileJava'.
> Receiver class com.palantir.gradle.jdks.ImmutableGradleJdksJavaInstallationMetadata does not define or inherit an implementation of the resolved method 'abstract boolean isCurrentJvm()' of interface org.gradle.jvm.toolchain.JavaInstallationMetadata.

This is because Gradle have added a method to JavaInstallationMetadata with no default, probably not expecting people to implement it :(.

After this PR

==COMMIT_MSG==
Support Gradle 8, avoid errors of the form "ImmutableGradleJdksJavaInstallationMetadata does not define or inherit an implementation of the resolved method 'abstract boolean isCurrentJvm()'"
==COMMIT_MSG==

Do this by making a dynamic proxy, which should work provided nothing actually calls these extra methods.

Related fix in baseline: palantir/gradle-baseline#2605

Possible downsides?

Wonderful hackery.

[changelog-app]

Generate changelog in changelog/@unreleased

What do the change types mean?

• feature: A new feature of the service.
• improvement: An incremental improvement in the functionality or operation of the service.
• fix: Remedies the incorrect behaviour of a component of the service in a backwards-compatible way.
• break: Has the potential to break consumers of this service's API, inclusive of both Palantir services
  and external consumers of the service's API (e.g. customer-written software or integrations).
• deprecation: Advertises the intention to remove service functionality without any change to the
  operation of the service itself.
• manualTask: Requires the possibility of manual intervention (running a script, eyeballing configuration,
  performing database surgery, ...) at the time of upgrade for it to succeed.
• migration: A fully automatic upgrade migration task with no engineer input required.

Note: only one type should be chosen.

How are new versions calculated?

• ❗The break and manual task changelog types will result in a major release!
• 🐛 The fix changelog type will result in a minor release in most cases, and a patch release version for patch branches. This behaviour is configurable in autorelease.
• ✨ All others will result in a minor version release.

Type

• Feature
• Improvement
• Fix
• Break
• Deprecation
• Manual task
• Migration

Description

Support Gradle 8, avoid errors of the form "ImmutableGradleJdksJavaInstallationMetadata does not define or inherit an implementation of the resolved method 'abstract boolean isCurrentJvm()'"

Check the box to generate changelog(s)

• Generate changelog entry

[felixdesouza]

I'm not sure I understand, why do we have to reimplement this? Didn't we do this in palantir/gradle-baseline#2605 ?

[felixdesouza]

sorry, accidentally closed

[CRogers]

We implement JavaInstallationMetadata in this repo too, so have the wrong incorrect inferface issue too.

[felixdesouza]

👍

[svc-autorelease]

Released 0.34.0