Repository navigation
Add Spring to Quarkus migration skill and HTTP verification - #7
Merged
Merged
Conversation
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.
Add a separately installable Spring-to-Quarkus migration skill. It guides the choice between native CDI/Jakarta REST and documented Spring compatibility extensions, flags unsupported Spring infrastructure, and requires behavioural checks before claiming a migration complete.
The package links official Quarkus documentation and the upstream quarkusio/skills project without copying or automatically installing it. Register it in the catalogue and add a Java 17 CI job comparing the existing Spring Boot 3.5.16 HTTP baseline with a new native Quarkus 3.40.1 fixture. Pages will regenerate after merge to main.
Validation: 17 skills structurally checked; all five new package resources pass APM content audit; all 10 Python tests pass; local Maven verification passes one HTTP test per framework with zero failures/errors/skips; Quarkus package builds. Browser checks verify discovery and installation command. Bandit, secrets and workflow scans have no unresolved findings. Hosted CI repeats validation and dependency auditing for this revision.
Evidence is bounded to constructor injection, JSON success/content type and missing-route HTTP behaviour. Compatibility extensions, authentication, persistence, reactive execution, native images, Gradle/Kotlin, performance and production deployment are not tested by this fixture. The skill remains experimental with long-term named ownership unassigned. Python dependency scans do not certify JVM dependencies.
Hosted checks passed for commit 524c00c: validation, security and framework tests and Pages build. Pages publication is deferred until merge. Local declared Python dependency audit found no known vulnerabilities.