You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Slawomir Jaranowski (Jira)" <ji...@apache.org> on 2023/01/12 12:36:00 UTC
[jira] [Commented] (MPLUGIN-451) Make prerequisite mandatory by default
[ https://issues.apache.org/jira/browse/MPLUGIN-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17675988#comment-17675988 ]
Slawomir Jaranowski commented on MPLUGIN-451:
---------------------------------------------
duplicates of MPLUGIN-418
> Make prerequisite mandatory by default
> --------------------------------------
>
> Key: MPLUGIN-451
> URL: https://issues.apache.org/jira/browse/MPLUGIN-451
> Project: Maven Plugin Tools
> Issue Type: Improvement
> Components: Plugin Plugin
> Reporter: Tamas Cservenak
> Priority: Major
>
> The POM maven/prerequisite field (applicable only to maven-plugin packaged artifacts) will become more and more important, especially when 3.9.x and 4.0.x possibly start to coexists.
> Similar to MPLUGIN-450 it is best practice if plugin has it defined to make potential error messages clear to end users (ie. tries to use plugin made for Maven 4 in Maven 3.9 or so).
> Unsure is there sense to make plugins without prerequisite, before, Maven2 plugins worked nicely in Maven3, but in Maven4 at some point (maybe in Maven5) we will have a disruption, and close up the guts of Maven and allow only API usage, making plugins incompatible with pre-4 Maven versions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)