Skip to content

Java Pack

Jump to bottom
issuelens[bot] edited this page Oct 14, 2026 · 7 revisions

Java Pack

Version and release-note provenance

At source commit ed0dc05edbf1cdf9349dd660fc7c15bcf385a8fe, the extension manifest's version is 0.31.2. The CHANGELOG.md section 0.31.2 associates that version with project-JDK selection/inventory synchronization and Refresh JDKs (#1777), tooling guidance for Language Support for Java 1.57 and runtime reporting/startup-view changes (#1768), and restored HTTPS TLS certificate validation (#1717). See Java Runtime Requirements for the separately sourced runtime details. These are version metadata and changelog associations, not independent verification of every referenced fix or evidence of Marketplace publication, release availability, deployment, or test execution.

Source: microsoft/vscode-java-pack, package.json, version, and CHANGELOG.md, 0.31.2; full merged/source-tip commit ed0dc05edbf1cdf9349dd660fc7c15bcf385a8fe, PR #1779, source identity microsoft/vscode-java-pack#1779:ed0dc05edbf1cdf9349dd660fc7c15bcf385a8fe. The complete three-file PR inventory (CHANGELOG.md, package-lock.json, package.json) was inspected with single-file paging and stable base/head/merge identities rechecked afterward. This PR changes release notes and version fields, not product implementation; it does not supersede the separately documented runtime behavior or maintenance workflow.

Automated validation

See Development and Validation for the pack repository's Java 27 AutoTest plans, project-JDK versus language-server-runtime boundary, test-only document-reopen helper, and E2E artifact troubleshooting. This records test configuration, not a product-support or release claim. Source: PR #1767, Java 27 fixture and validation guide, full source commit eb203464c082d7aa98d15202236a8bdeb91b3b56.

The same validation page also covers npm test (node --test), mocked runtime/toolchain regression checks, and the Java 21/25 Gradle import/task-model/build plans with shared CI toolchain bindings. Source: PR #1768, tests/, test-plans/, full source commit a1fd732e13a2cf9b73c9762d3de3cb445acea545. These are source-backed checks, not observed test results.

Go to Super Implementation hover-link regression

Run autotest run test-plans/java-go-to-super-implementation.yaml for the pack-owned UI regression plan targeting the hover link contributed by redhat.java. The plan declares AutoTest 0.7.32+ for state-driven hover and active-tab verification; its setup uses stable VS Code, pre-release extension coverage, and test-fixtures/super-implementation. This is test configuration, not verification of AutoTest internals, an observed test pass, or a product fix/release claim.

After waitForLanguageServer, open-derived requires Derived.java to be active and contain public void greet. click-super-link uses hoverAndClickAction "greet" "Go to Super Implementation" with a 30-second timeout rather than separate hover/click steps or a substitute navigation command. The plan's readiness criterion is the actual clickable link, not a visible popup or loading text. Both that step and verify-base-open require Base.java as the active editor tab; the final assertion also checks Hello from Base and uses wait 0 seconds with skipLlmVerify: true. A background tab alone does not satisfy these configured assertions.

Source: microsoft/vscode-java-pack, test-plans/java-go-to-super-implementation.yaml, setup and steps open-derived, click-super-link, verify-base-open; full merged/source-tip commit dc8ddca308d96f056420e552cbde845aeae77018, PR #1774, source identity microsoft/vscode-java-pack#1774:dc8ddca308d96f056420e552cbde845aeae77018. The plan identifies upstream issue redhat-developer/vscode-java#4438 as its regression target and references #4440 as the product fix; those upstream implementation/release claims were not independently verified here. PR #1774 changes only this plan, not tooling-JDK selection or product navigation implementation.

Runtime setup and help UI

See Java Runtime Requirements for the shared tooling-minimum matrix, FAQ, current project-JDK configuration route, and restored legacy runtime tabs. Java Pack owns this guidance/UI, not the language client's runtime selection or startup diagnostics. Its legacy view reads already-active redhat.java runtime metadata without probing tooling candidates; explicit tooling-JDK selection remains separate from project-JDK configuration. Source: PR #1768, src/java-runtime/utils/upstreamApi.ts, getRequiredJdkVersion() / getToolingRuntimeInfo(), and src/java-runtime/index.ts, full source commit a1fd732e13a2cf9b73c9762d3de3cb445acea545. Merge does not establish release or deployment.

Team-memory maintenance workflow

Java Pack separates source-push dispatch from central reconciliation. Both workflows require ISSUELENS_TEAM_MEMORY_COORDINATOR_ENABLED == 'true', repository microsoft/vscode-java-pack, and a ref matching the repository's default branch. The legacy ISSUELENS_TEAM_MEMORY_ENABLED gate no longer activates this caller. These are repository workflow configurations, not proof of enablement, deployment, or successful wiki publication. [1][2]

Source-push dispatcher

.github/workflows/team-memory-post-merge.yml is named Queue Java team memory (opt-in) and triggers only on pushes to main; it no longer provides manual dispatch. Its dispatch job additionally requires a push event, github.workflow_sha == github.sha, and false created, deleted, and forced flags. The explicit main trigger and coordinator ref do not automatically follow a default-branch rename. [1]

The job uses ubuntu-latest, a 10-minute timeout, and job permissions contents: read and actions: write, with empty workflow-level permissions. Its sole step invokes microsoft/IssueLens/.github/actions/queue-team-memory pinned to a81d2d96167fc0e69ac631c2edc85f858e693289. It uses the job token to dispatch team-memory-coordinator.yml in microsoft/vscode-java-pack at main, passing string fields source_repository, source_run_id, source_run_attempt, push_before (event before), and push_after (github.sha). Azure/agent invocation is no longer configured in this source job. [1]

Central coordinator and manual recovery

.github/workflows/team-memory-coordinator.yml, named Coordinate Java team memory (opt-in), accepts workflow_dispatch. The required string source_repository defaults to microsoft/vscode-java-pack. Automatic dispatch supplies source_run_id, source_run_attempt, push_before, and push_after; the input descriptions require an attempt and head SHA with a run ID. For manual single-PR reconciliation, supply source_repository and pull_request_number for a merged source PR instead of the automatic source-run/range inputs. These optional fields are declared as strings; downstream validation is delegated to the shared action. push_before is explicitly described as a requested reconciliation ancestor, not an attested original push boundary. [2]

Automatic and manual requests use the same fixed workflow concurrency group, issuelens-team-memory-wiki-microsoft-vscode-java-pack, with queue: max and cancel-in-progress: false. This replaces the source workflow's per-range/per-PR concurrency group; the source dispatcher itself no longer declares concurrency. [1][2]

The reconcile job requires workflow_dispatch, runs on ubuntu-latest with a 30-minute timeout, and grants contents: read, pull-requests: read, actions: read, and id-token: write; workflow-level permissions remain empty. Its configured source-name/repository-ID map is: [2]

Source repository Repository ID
microsoft/vscode-java-pack 104967329
microsoft/vscode-java-debug 102584737
microsoft/vscode-java-test 110522074
microsoft/vscode-java-dependency 129053101
microsoft/vscode-maven 116921700
microsoft/vscode-gradle 216314492
microsoft/java-debug 102583752
microsoft/build-server-for-gradle 626812412

The coordinator now passes its built-in ${{ github.token }} as source-github-token for both Java Pack and external allowlisted public-source reads. PR #1775 removed the local source-selection shell step and external-source actions/create-github-app-token step; the coordinator no longer references or requires ISSUELENS_SOURCE_READ_APP_CLIENT_ID or ISSUELENS_SOURCE_READ_APP_PRIVATE_KEY. The source name and unchanged map are passed directly to the shared action, with no local allowlist check remaining. This is coordinator wiring, not evidence of other repositories' caller configuration or private cross-repository access. [5]

The sole step directly invokes microsoft/IssueLens/.github/actions/issuelens at a81d2d96167fc0e69ac631c2edc85f858e693289, with request-type: team-memory, the source map, the built-in job token for both github-token and source-github-token, all reconciliation inputs, output-mode: activity, and summary-mode: status. It references AZURE_CLIENT_ID, AZURE_TENANT_ID, AZURE_SUBSCRIPTION_ID, ISSUELENS_AGENT_URL, and ISSUELENS_AGENT_SCOPE. Neither workflow contains a checkout step or local implementation of the shared actions. [1][5]

Validation boundary and superseded configuration

The complete PR #1769 file inventory comprises the two workflows above; both were verified at merged source commit 7c60d51b73fad09b2e89771ac162956a8ad7f994, the supplied source-tip revision for that review. This establishes the caller wiring, not the external action implementation, runtime receipt-validation behavior, delivery guarantees, App installations, secret availability, Azure/OIDC federation readiness, or successful execution. A merge or accepted dispatch alone does not establish wiki publication. [1][2][3]

PR #1775 supersedes only the coordinator's source-read authentication described by PR #1769. Its complete one-file patch and coordinator source at merged/source-tip commit dce06dedc1c90fc80edc8a9a6aab1ce3154039f8 confirm the token change; the gates, permissions, concurrency, eight-entry source map, inputs, action pin, Azure/agent references, and output modes remain unchanged. Removing workflow references does not establish removal of stored secrets or installed Apps, change source-dispatch credentials, or prove successful metadata reads or end-to-end execution. Shared-action internals and external callers were not revalidated for this change. [5]

This supersedes the PR #1763 configuration: Update IssueLens Team Memory previously invoked issuelens directly at 2b5317815e15179899014a02c41678620ce2d390, retained manual PR dispatch in the source workflow, and used the legacy gate and per-range/per-PR concurrency. Use the coordinator entry point above rather than that historical recovery route. [1][3][4]

Source

Clone this wiki locally