fix: upgrade foojay-resolver-convention to 1.0.0

[TheNerdGuyLulu]

Summary:

foojay-resolver-convention's version 0.5.0 is not compatible with Gradle 9. (gradle/foojay-toolchains#151)
When trying to build for Android on React Native 0.8.2, we are presented with

java.lang.NoSuchFieldError: Class org.gradle.jvm.toolchain.JvmVendorSpec does not have member field 'org.gradle.jvm.toolchain.JvmVendorSpec IBM_SEMERU'
	at org.gradle.toolchains.foojay.DistributionsKt.<clinit>(distributions.kt:16)
	at org.gradle.toolchains.foojay.FoojayApi.fetchDistributionsIfMissing(FoojayApi.kt:62)
	at org.gradle.toolchains.foojay.FoojayApi.match$foojay_resolver(FoojayApi.kt:49)
	at org.gradle.toolchains.foojay.FoojayApi.toLinks(FoojayApi.kt:41)

Changelog:

Test Plan:

After making the change, the app build without problems.

[meta-cla]

Hi @TheNerdGuyLulu!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[meta-cla]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

[cortinico]

I don't believe this is needed for Gradle 9.0.0
We shipped it in 0.82 with Gradle 9.0.0 and we never needed to bump this

[TheNerdGuyLulu]

Hi @cortinico,

It might be related to usage with openjdk@25. Apparently works fine with openjdk@21.
But I'm getting a new error with openjdk@25, can't test it.

A problem occurred evaluating project ':react-native-reanimated'.
> A problem occurred starting process 'command 'node'' * Try:

[cortinico]

It might be related to usage with openjdk@25. Apparently works fine with openjdk@21.
But I'm getting a new error with openjdk@25, can't test it.

Open JDK 25 is not supported yet sadly

[sschuberth]

I don't believe this is needed for Gradle 9.0.0

I believe it is, see e.g.

• https://docs.gradle.org/current/userguide/upgrading_major_version_9.html#removal_of_deprecated_jvmvendorspec_ibm_semeru
• Task updateDaemonJvm fails with JvmVendorSpec does not have member field 'org.gradle.jvm.toolchain.JvmVendorSpec IBM_SEMERU' gradle/gradle#35596 (comment)
• Gradle 9.1.0 build fails on Mac because of NoSuchFieldError: JvmVendorSpec IBM_SEMERU gradle/gradle#35726 (comment)

The issue only surfaces if Gradle's toolchain mechanism is actually triggered to bootstrap a JDK in the desired version via the foojay resolver.

So can we please reopen this @cortinico?

[cortinico]

The issue only surfaces if Gradle's toolchain mechanism is actually triggered to bootstrap a JDK in the desired version via the foojay resolver.

So can we please reopen this @cortinico?

@sschuberth can you open a new PR please. We do have a dedicated workflow that triggers whenever a new PR gets opened and it would help us make sure this gets addressed

[TheNerdGuyLulu]

@cortinico @sschuberth
#56210