Repository navigation
Conversation
qanary-component-LD-Java now builds against qa.component 5.0.2, the release with Spring Boot 4.1.0 and Spring Boot Admin 4.1.2. The comments in build.sh, the Dockerfile, the pom and the README still said the framework (4.0.0) was a local build missing from Maven Central. It has been resolved from Maven Central for some time (the CI builds on a clean runner); they now say so and no longer ask for a local install.
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
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.
Updates the Java component to the new Qanary release and corrects outdated build notes.
qanary-component-LD-Java/pom.xml:qanary.version5.0.1 → 5.0.2 (Spring Boot 4.1.0, Spring Boot Admin 4.1.2; published on Maven Central 2026-10-27). The e2e tests already useqanary/qanary-pipeline:latest, which is 5.0.2 now.build.sh,qanary-component-LD-Java/Dockerfile,README.adoc: the notes still said the framework was a local build missing from Maven Central and asked for a localmvn install. It is resolved from Maven Central (the CI builds on a clean runner), so the notes now say so.