You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit a1fd732
Browse filesBrowse the repository at this point in the historyBrowse files
fix: tooling JDK requirements and runtime selection for redhat.java 1.57 (#1768)
* fix: align tooling JDK requirements with redhat.java
* fix: leave language-server runtime selection to redhat.java
* fix: limit runtime guidance to upstream-reported information
* test: use state-driven super implementation navigation
* fix: preserve manual JDK setup without runtime metadata
* test: verify compatible Gradle JDK imports and builds
Keep Gradle 8.5 with a JDK 21 daemon and test a real Java 25 project with Gradle 9.8.1. Assert generated import metadata, dependency-backed completion, clean builds, runtime output and target bytecode. Provision matching CLI/JDK paths in CI without changing automatic JVM selection.
* fix: preserve project controls and clarify JDK configuration guidance
* ci: prepare VSIX overrides once for the UI matrix
* test: bind Gradle UI cases to the CI toolchain
* test: repair Gradle model configuration and verify IDE health
* chore: split CI preparation and navigation coverage into separate PRs
* fix: preserve tooling metadata on project inventory errors
* fix: align legacy javac-mode JDK requirements with upstream
* ci: consolidate Gradle toolchain binding for JDK 21/25/27
* ci: remove extra tool binding and move runtime guidance to wiki
Copy file name to clipboardExpand all lines: .github/skills/uitest/SKILL.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,3 +77,6 @@ The repository workflow `.github/workflows/e2e-autotest.yml` builds a branch VSI
77
77
78
78
Use workflow dispatch when the user asks to validate in CI or across platforms. The `test_plan` input can target a single plan; leave it empty to run all plans.
79
79
80
+
For `java-gradle`, `java-gradle-java25`, and `java-gradle-java27`, CI uses one Gradle setup and the existing environment-binding mechanism. Java 21/25 helpers read `GRADLE_CI_GRADLE`, their `JAVA21_HOME`/`JAVA25_HOME`, and `AUTOTEST_STAGING_DIR`; the Java 27 helper retains its `JAVA27_CI_GRADLE` contract. CI does not rewrite terminal commands or override the IDE's Gradle home. Actual version, program-output and bytecode assertions remain unchanged. Local helper invocations retain their existing behavior.
81
+
82
+
For Java 21/25, the same binding exports `ORG_GRADLE_PROJECT_javaRelease` before VS Code starts. Local runs must set that project property as documented in the fixture README. These plans require BSP import, actual Gradle `build`/`run` tasks, and the exact configuration marker in Gradle for Java output; terminal success alone is insufficient. All three Gradle plans reuse the shared artifact collector: terminal diagnostics are staged outside AutoTest's output and archived under `diagnostics/ci/terminal/`, while Gradle/Java output-channel and extension-host logs are archived under `logs/ide/logs/`.
if ($versionExit -ne 0) { throw "CI Gradle version probe exited with $versionExit; see diagnostics/ci/gradle-version.log in this case's results artifact." }
233
-
if ($gradleVersion -notmatch '(?m)^Gradle 9\.8\.1\s*$') {
234
-
throw "CI did not select the provisioned Gradle 9.8.1: $ciGradle; see $versionLog"
if ($versionExit -ne 0) { throw "CI Gradle version probe exited with $versionExit; see diagnostics/ci/gradle-version.log in this case's results artifact." }
250
+
if ($gradleVersion -notmatch '(?m)^Gradle 9\.8\.1\s*$') {
251
+
throw "CI did not select the provisioned Gradle 9.8.1: $ciGradle; see $versionLog"
Copy file name to clipboardExpand all lines: README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,6 +63,8 @@ At the same time, [📦 CheckStyle](https://marketplace.visualstudio.com/items?i
63
63
64
64
## Questions & Issues
65
65
66
+
See the [Java runtime requirements and configuration](https://github.com/microsoft/vscode-java-pack/wiki/Java-Runtime-Requirements) guide for JDK setup details.
67
+
66
68
Each extension mentioned above is a separate open-source project and has its own repository. To make things easier, simply [🙋 open an issue in this repository](https://github.com/Microsoft/vscode-java-pack/issues). The new issue will be triaged and redirected.
@@ -50,12 +51,15 @@ export default function FaqPanel() {
50
51
51
52
<h2className="font-weight-light">Why do I see the JDK errors?</h2>
52
53
<p>
53
-
<strong><code>JDK {REQUIRED_JDK_VERSION}+</code> is required</strong> to run the Java language support (redhat.java) extension! You see this error because we failed to find one on your machine. The <ahref="command:java.runtime">Configure Java Runtime</a> guide can help you understand how JDK path is searched and provides download links if you need to install one.
54
+
<strong><code>JDK {requiredJdkVersion}+</code> is required</strong> to run the installed Java language support (redhat.java) extension. A compatible bundled runtime can satisfy this requirement; otherwise, a compatible local JDK is needed. To set the language-server launch JDK explicitly, configure <ahref={toolingSettingsCommand}><code>java.jdt.ls.java.home</code></a>. Runtime selection and startup diagnostics are provided by redhat.java; <ahref="command:java.open.logs">open the Java logs</a> for details.
55
+
</p>
56
+
<p>
57
+
The <ahref="command:java.runtime">Configure Java Runtime</a> page configures project JDKs, not the language-server launch JDK. Your projects can use older JDKs independently of the tooling requirement.
54
58
</p>
55
59
56
60
<h2className="font-weight-light">Can I run my Java 8 project with JDK 1.8?</h2>
57
61
<p>
58
-
Yes. The JDK {REQUIRED_JDK_VERSION} requirement is just for running the Java language support (redhat.java) extension itself. You can still configure a different runtime <ahref="command:java.helper.openUrl?%22https%3A%2F%2Fcode.visualstudio.com%2Fdocs%2Fjava%2Fjava-project%23_jdk-for-projects%22">JDK for your project</a> via the user setting <ahref="command:workbench.action.openSettings?%22java.configuration.runtimes%22">"java.configuration.runtimes"</a>. The extension will pick a matching JDK to compile/run your project according to the compiler version specified by the project build file.
62
+
Yes. The JDK {requiredJdkVersion} requirement is just for running the Java language support (redhat.java) extension itself. You can still configure a different runtime <ahref="command:java.helper.openUrl?%22https%3A%2F%2Fcode.visualstudio.com%2Fdocs%2Fjava%2Fjava-project%23_jdk-for-projects%22">JDK for your project</a> via the user setting <ahref="command:workbench.action.openSettings?%22java.configuration.runtimes%22">"java.configuration.runtimes"</a>. The extension will pick a matching JDK to compile/run your project according to the compiler version specified by the project build file.
0 commit comments