[
https://issues.apache.org/jira/browse/MPLUGIN-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17843885#comment-17843885
]
Tamas Cservenak edited comment on MPLUGIN-522 at 5/7/24 8:07 AM:
-----------------------------------------------------------------
Example: try with Maven4 + Java 21: {{mvn
eu.maveniverse.maven.plugins:toolbox:tree}} and it will explode, claiming
"plugin requires Java 22". Now use Java 11 and Maven 3.6.3, and plugin works!
was (Author: cstamas):
Example: try with Maven4 + Java 21: {{mvn
eu.maveniverse.maven.plugins:toolbox:tree}} and it will explode, claiming
"plugin requires Java 22". Now use Java 11 and Maven 3.9.6, and plugin works!
> 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)
