apache / apache/maven-plugin-tools

[MPLUGIN-350] Extend @Parameter with input/output option

未关闭
#653 18 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
enhancement priority:major
主要语言
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

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。