quarkusio/quarkus

Picocli extension - consider generating command metadata during build

Open

#16,355 建立於 2021年4月8日

在 GitHub 查看
 (22 留言) (0 反應) (0 負責人)Java (12,967 star) (2,464 fork)batch import
area/cligood first issuekind/enhancement

描述

ATM picocli builds the CommandSpec metadata using reflection every time the application is started. This is OK in most situations but may represent considerable overhead for applications that finish instantly, e.g. some Quarkus CLI commands. It might make sense to analyze the commands during build and either generate some "builder" classes or record the metadata (e.g. using AnnotationProxyBuildItem) and build the metadata in a recorder method.

貢獻者指南

技術棧
java
領域
cliperformancebuild system
議題類型
performance
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
3-5 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Java programmingQuarkus frameworkPicocli libraryBuild time optimization concepts
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
Investigate the current picocli extension in Quarkus (e.g., in extensions/picocli/). Look at the existing CommandSpec creation during startup. Explore the use of AnnotationProxyBuildItem for capturing metadata at build time. Review the discussion in the issue comments for alternative approaches. Consider implementing a BuildStep that generates the command metadata and stores it in a recorder.