[
https://issues.apache.org/jira/browse/MPLUGIN-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17305429#comment-17305429
]
Arnaud Heritier commented on MPLUGIN-350:
-----------------------------------------
I agree that the granularity of the description is important and more granular
infos we have better we can control the behavior.
But let's be honest, we don't necessarily have to target something ideal from
the beginning (it's often the problem we have in maven ecosystem to try to do
things perfects from the beginning - it's good because we rarely have to
update/break our features but it's bad because the project moves very slowly).
On this topic we have also the advantage to not be precursors on this topic and
we can look at what others are doing like Gradle:
https://docs.gradle.org/current/userguide/more_about_tasks.html#sec:up_to_date_checks
> 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)