[
https://issues.apache.org/jira/browse/MPLUGIN-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17305736#comment-17305736
]
Romain Manni-Bucau commented on MPLUGIN-350:
--------------------------------------------
[~rfscholte] ok to scope this ticket to plugin and have another umbrella ticket
for input/output support (this one becoming a subtask?). eval mojo is a great
example that you can mark input params but not output so overall plugin
contribution is not accurate. Add to that the fact your input is incomplete and
not sufficient for a graph approach (keep in mind most of the scripting engines
will supports imports/includes which are not made mojo aware). This is why I
mentionned that this API is not required to start supported input/output in
maven but that explicitly binding them per module is the main prerequisite (and
that deducing them when not set by checking mojo values can be an
implementation optimization but not the first impl). The fact to fallback on
"not maven context aware" is for not not an option since almost all builds will
fall in this bucket in practise so feature would never be usable as mentionned.
> Extend @Parameter with input/output option
> ------------------------------------------
>
> 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)
