apache / apache/maven-plugin-tools
[MPLUGIN-350] Extend @Parameter with input/output option
- 主要語言
- Java
- 星號
- 64
- 分支
- 71
- 平均合併
- 12 小時 24 分鐘
- 30 天內合併 PR
- 32
描述
**[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** opened **[MPLUGIN-350](https://issues.apache.org/jira/browse/MPLUGIN-350?redirect=false)** and commented
By knowing if parameters are input or output parameters, it is possible to improve our builds. It will be possible to create DAGs and chain the execution blocks much smarter.
The Maven Extension created by Gradle heavily relies on this kind of information.
It is probably easier to use new annotations instead of adding a (required) status-field to `@Parameter`
Looking at the `plugin.xml` it looks quite easy to solve this and stay backwards compatible: the file looks now like:
```xml
...
```
With plexus-magic the following should still work:
```xml
...
...
```
Input parameters should refer to the outputParameter it effects. E.g. if a inputParameter has only effect on the logger and it is changed, it will not effect the resulting artifact, which could improve faster incremental builds.
---
0 votes, 6 watchers
貢獻指南
這個儲存庫沒有索引到貢獻指南
研究方向
首先定位 @Parameter 註解以及 issue 中描述的 plugin.xml 產生或表示方式。確定應如何表示輸入參數和輸出參數,同時保留現有的參數格式,包括輸入參數如何參照受影響的輸出。完成標準是中繼資料能夠表達這些關係,並保持向後相容。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- java
- 領域
- build-system, devtools
- Issue 類型
- 功能
- 難度
- 5/5
- 預估耗時
- 一週以上
- 活躍度
- 停滯
- 描述清晰度
- 基本清楚
- 新手友好度
- 25/100