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

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

There are 2 topics: how to mark plugins as input or output parameter, and how 
to store it.
For the latter there is problably only one solution: add a new element inside 
the {{<parameter>}}-block, as this is the only backwards compatbile solution.
And I wonder if we need to know if we need to bind input to their output 
(defaults to all). For example: verbose is output logging and doesn't effect 
the artifact result. In such case we could ignore the verbose flag in case were 
interested in the artifacts.
This is optimization, so first make it work. But we should keep in mind that we 
might need such features in the future.

> 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)

Reply via email to