[
https://issues.apache.org/jira/browse/MPLUGIN-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17305407#comment-17305407
]
Romain Manni-Bucau commented on MPLUGIN-350:
--------------------------------------------
I think it must be added to pom model instead of plugin first (can be cumulated
but general solution is pom) since some plugins have no way to know like exec,
scripting etc...
Also some output can be ignored - thinking to jib debug .properties/json.
So overall it looks like it is a module concern and not a mojo concern since
maven is module driven (whereas grafle is task/mojo driven so we must not copy
thzir model IMHO).
> 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)
