-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
None
-
Quarkus target - Target Runtime Label and replacing non-Spring artifacts with Quarkus extensions
-
False
-
False
-
To Do
-
67% To Do, 0% In Progress, 33% Done
-
Undefined
-
Priority Backlog
There has been a comprehensive set of rules developed for the SpringBoot to Quarkus migration path under Epic WINDUPRULE-473
The purpose of this EPIC is to
- Further enhance the rulesets to identify other migration paths to for adopting quarkus modules (e.g. org.apache.avro to quarkus.avro)
- Develop a Quarkus Target runtime label
To support this we need to enhance the technology identification tag rules to identify the relevant technologies that we know are, or are not supported by quarkus.
Particular emphasis must be on identifying the Spring/SB technologies referenced in our SB2Quarkus rulesets. When the technology tags are in place then creating a Quarkus Target Runtime Label will be very straight forward.