[
https://issues.apache.org/jira/browse/MPLUGIN-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17305553#comment-17305553
]
Romain Manni-Bucau commented on MPLUGIN-350:
--------------------------------------------
Which hack? Concretely my point is to target what users can rely on and not try
to be idealistic and do something almost no project but commons can use.
Inputs/outputs from tasks (mojo) always lead to wrong build setups in practise,
always. Workaround is to drop the cache but it is not a feature as such for me.
Ensuring build owns that feature and usage makes it usable and useful for end
users. In that regard using mojo level first is a hack ;).
> 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)
