Build Java detector JAR in CI - #223
Merged
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 92cb6f75-a323-4fd4-aa92-838909bba222
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 checked-in Java version detector JAR can drift from its source because the existing JAR workflow only builds the site generators.
Rename the workflow to
Build Project JARsand add a Temurin Java 8 job that compiles, packages, and verifies the detector. The job compares compiled classes with the shipped JAR before rebuilding, preventing timestamp-only commits, and pushes a bot commit tomainonly when the tracked JAR genuinely changes. The deploy workflow now follows the renamed build workflow.