Problème pour déterminer Java 11.0.10

Help/Discuss
1

problème pour déterminer la version de 15.0.2

Bonjour j’ai un problème avec la commande gradlew setupDecompWorkspace, en exersant cette commande j’ai le message d’erreur suivant:

Picked up _JAVA_OPTIONS: -Xmx4096m

FAILURE: Build failed with an exception.

  • What went wrong:
    Could not determine java version from ‘15.0.2’.
  • Try:
    Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

J’ai créer dans la Variable Environnement un

                                          - _JAVA_OPTIONS avec comme variable: -Xmx4096m

                                          -JAVA_HOME avec comme variable: C:\Program Files\Java\jdk-15.0.2\
                                          
                                          -Path avec comme variable: C:\Program Files\Java\jdk-15.0.2\bin
                                            
                                                                     C:\Program Files\Java\jre1.8.0_281\bin

Ma version de gradle est la 2.14

Ma version JDK/JRE
-15.0.2 (JDK)
-1.8.0_281 (JRE)

Mon gradle-wrapper contient:
#Mon Sep 14 12:28:28 PDT 2015
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https://services.gradle.org/distributions/gradle-2.14-bin.zip

J’ai regarder beaucoup de tuto comment installer JRE/JDK mais aucun de ces tutos ne m’ont aidé à résoudre se problème.

2

Je viens de trouver la raison qui cause le: Erreur : impossible de déterminer la version Java à partir de «15 .0.2». Il faut pour sa revenir à une plus ancienne version: 8.271. Il vous fournira le JRE et le JDK avec la même version.
lien vers 8.271: Télécharger gratuitement Java Development Kit (JDK) 8 Update 271 pour Windows

3

My French is pretty rusty, but from what I understood, your problem is that you try to run a build that uses an ancient Gradle version (2.14) with Java 15.0.2. Gradle added compatibility with Java 15 in version 6.7.

4

How do I go from gradle version 2.4 to version 6.7?

5

For upgrading from 4.x and newer there more exist dedicated upgrade notes at Gradle User Manual: Version 6.8.3.

Generally a good tactic is to upgrade to latest 2.x, fix all deprecation warnings, upgrade to latest 3.x, fix all deprecation warnings, and so on.
Because except of edge cases, a build should run with the next major version if it is on the latest minor release and has no deprecation warnings.

7

I still have the same error even when changing my version of my gradle.

8

I have used the gradle wrapper --gradle-version 6.8.3 command to update the project to version 6.8.3. And its my put this error: FAILURE: Build failed with an exception.

  • Where:
    Build file ‘C: \ Users \ User \ Desktop \ Minecraft \ version \ 1.12 \ 1.12.2 \ Time Death \ build.gradle’ line: 10

  • What went wrong:
    A problem occurred evaluating root project ‘Time Death’.

‘org.gradle.api.tasks.TaskOutputs org.gradle.api.internal.TaskOutputsInternal.dir (java.lang.Object)’

  • Try:
    Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

  • Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use ‘–warning-mode all’ to show the individual deprecation warnings.
See Command-Line Interface

9

You didn’t include the actual error above that message. And consider including such output into a code block so that it is not rendered as if it were markdown, which makes it pretty hard to read.

10

Could the problem be with gradle-wrapper:
#Sun Feb 28 12:05:59 CET 2021
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https://services.gradle.org/distributions/gradle-3.0-bin.zip

11

I have no idea, as you still did not provide the actual error.
Besides that, if you want to go from 3.0 directly to 6.8.3 there can of course be some problems, that’s why I suggested the incremental process described above.