[jira] [Commented] (MPLUGIN-350) Split @Parameter into @Input and @Output

["Robert Scholte (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MPLUGIN-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16869354#comment-16869354 ] 

Robert Scholte commented on MPLUGIN-350:
----------------------------------------

There might be a third category, one that doesn't effect the output. Some plugins have a {{verbose}} parameter which increases the logging while the resulting files are the same. There are likely similar parameters in this category.

> 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
(v7.6.3#76005)