quarkusio/quarkus

Add a property for the version when creating a project with a non-platform extension

Open

#39,439 建立於 2024年3月14日

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

描述

Description

Currently when adding a non-platform extension, the version is hard-coded:

<dependency>
      <groupId>io.quarkiverse.web-bundler</groupId>
      <artifactId>quarkus-web-bundler</artifactId>
      <version>1.3.1</version>
    </dependency>

It would be nice to have the version as a property instead:

...
<properties>
    ....
    <quarkus-web-bundler.version>1.3.0</quarkus-web-bundler.version>
</properties>
...
<dependency>
      <groupId>io.quarkiverse.web-bundler</groupId>
      <artifactId>quarkus-web-bundler</artifactId>
      <version>${quarkus-web-bundler.version}</version>
    </dependency>

I guess this could also be done when adding an extension on an existing project.

Implementation ideas

No response

貢獻者指南

技術棧
java
領域
backendbuild system
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
JavaMavenQuarkus extension mechanism
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
Investigate the Maven plugin code that generates project pom.xml files. The version for non platform extensions is hardcoded; a property like ${quarkus web bundler.version} should be introduced. Look for similar property patterns in the codebase, and ensure the property is set based on the extension's version. Check the related comments in the issue for additional context.
Add a property for the version when creating a project with a non-platform extension · quarkusio/quarkus#39439 | Good First Issue