[
https://issues.apache.org/jira/browse/MPLUGIN-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17305412#comment-17305412
]
Tibor Digana commented on MPLUGIN-350:
--------------------------------------
Pls remember that the "input" and "output" must be qualified.
The reason is that the incremental build would not run the plugin if you alter
one parameter "verbose" because this parameter is only about loggin the plugin.
Similar with "readOnly" parameters, because these are for internal purpose.
So you do not need to add these two sections "input" and "output".
All you need is *to mark* the parameter:
1. is the parameter "input" or "output" (e.g. <target>input</target>).
2. qualifier, internal or build purpose (e.g. <purpose>internal<purpose>).
We can do the same with the list of params in the XML and add xml attributes
instead of elements.
This way the xml is backwards compatible
> Split @Parameter into @Input and @Output
> ----------------------------------------
>
> Key: MPLUGIN-350
> URL: https://issues.apache.org/jira/browse/MPLUGIN-350
> Project: Maven Plugin Tools
> Issue Type: New Feature
> Reporter: Robert Scholte
> Priority: Major
>
> 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:
> {code:xml}
> <parameters>
> <parameter>
> ...
> </parameter>
> </parameters>
> {code}
> With plexus-magic the following should still work:
> {code:xml}
> <parameters>
> <input>
> ...
> </input>
> <output>
> ...
> </output>
> </parameters>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
