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

**[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

Inizia individuando l’annotazione @Parameter e la generazione o rappresentazione di plugin.xml descritta nell’issue. Determina come devono essere rappresentati i parametri di input e output, preservando il formato dei parametri esistente, incluso il modo in cui i parametri di input fanno riferimento agli output interessati. Il lavoro è completato quando i metadati possono esprimere queste relazioni e rimangono retrocompatibili.

Scritto dal modello di indicizzazione a partire dal testo della issue.