[
https://issues.apache.org/jira/browse/MPLUGIN-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17844192#comment-17844192
]
Tamas Cservenak commented on MPLUGIN-522:
-----------------------------------------
Currently m-p-p produces plugins:
* that happily works on Java 11 w/ Maven 3.6.3
* but fails with Maven 4 (that observe these new entries in plugin descriptor)
due fals prerequisites: it claims it needs Java 22 and Maven 3.9.6, and none of
these are true
I, as a developer was totally oblivious of these auto-set values, until i tried
the plugin with Maven4.
> The auto prerequisites are way to aggressive
> --------------------------------------------
>
> Key: MPLUGIN-522
> URL: https://issues.apache.org/jira/browse/MPLUGIN-522
> Project: Maven Plugin Tools
> Issue Type: Bug
> Components: Plugin Plugin
> Reporter: Tamas Cservenak
> Priority: Major
>
> IMHO the implementation done in MPLUGIN-425 and MPLUGIN-424 are wrong.
> They are way too aggresive and violate backward compatibility: if new feature
> is not explicitly set by user, code should not "come up" with some automatic
> value. By having the value not set simply means user does not want to use it.
> This is especially true for (maven or java) prerequisite, as it creates HARD
> BREAKAGE if not met. Use of prerequisite is opt-in, but now it is FORCED onto
> user.
> [~kwin]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
