[TASK] Update cli to stable quarkus version supporting java 25 bytecode.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Description
The Quarks version we currently used only supports up to Java 21 bytecode. We can compile with Java 25. There may also need to be some changes in our source to update including changes from javax to jakarta namespaces. The quarkus cli has upgrade tooling to help make changes to the source code.
We currently have some common dependencies defined in the bom folder which are used for core and cli and this may be a problem as we are not yet ready to update core to jakarta versions that require Tomcat 10. We may need to decouple CLI a bit from core, which may not be a bad thing.
Acceptance Criteria
TOOD
Priority
None
Additional Context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the common dependencies in the bom folder and how they are consumed by core and cli. Check the Quarkus CLI upgrade tooling and identify the Java 25 and javax-to-jakarta migration requirements. Done should be defined as a stable Quarkus-based CLI that supports Java 25 without forcing incompatible core dependencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, cli
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100