Replace Python Java detector with Java 8 executable JAR - #220
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 63b24e01-23ba-45ce-8d37-5c89615389c1
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The modern Java agent plugin should be usable without requiring Python or a full JDK just to determine a project's target Java version.
This replaces the Python detector and tests with a dependency-free Java implementation compiled as an 11.7 KB Java 8 executable JAR. Cross-platform launchers provide actionable errors when Java is unavailable, while retaining the source for auditability. The release workflow compiles the source with a pinned JDK 8 toolchain, verifies its class files match the shipped JAR, runs the Java validation suite against that artifact, and confirms Java 8 bytecode compatibility.
The detector output remains compatible with the previous JSON contract and has been exercised on Java 8, 21, and 25. Plugin guidance, documentation, reference coverage, and the website example are updated for the new launch path.