[ 
https://issues.apache.org/jira/browse/MNG-4840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17830400#comment-17830400
 ] 

ASF GitHub Bot commented on MNG-4840:
-------------------------------------

kwin commented on PR #1444:
URL: https://github.com/apache/maven/pull/1444#issuecomment-2017511014

   As you can see in 
https://github.com/apache/maven/blob/eae39474cbb5a88048cea76709321f20e2f42b0b/maven-plugin-api/src/main/java/org/apache/maven/plugin/descriptor/PluginDescriptorBuilder.java#L42-L106
 this field was never evaluated by the parser (although already contained in 
the PluginDescriptor object). Therefore effectively prior to Maven 4 it is only 
ever set via 
https://github.com/apache/maven/blob/eae39474cbb5a88048cea76709321f20e2f42b0b/maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultMavenPluginManager.java#L191
 through the according POM field.
   Therefore I would keep documenting that this is only supported with Plugin 
Descriptor v1.1 and Maven 4 only. Prior it was just a shortcut for accessing 
the plugin's POM prerequisites element.




> Prerequisites is not working on m3
> ----------------------------------
>
>                 Key: MNG-4840
>                 URL: https://issues.apache.org/jira/browse/MNG-4840
>             Project: Maven
>          Issue Type: Bug
>          Components: POM
>    Affects Versions: 3.0-alpha-6, 3.0-alpha-7, 3.0-beta-1, 3.0-beta-2, 
> 3.0-beta-3
>            Reporter: velo
>            Assignee: Benjamin Bentmann
>            Priority: Major
>             Fix For: 3.0.2
>
>         Attachments: mng-001.zip, testapp.tar
>
>
> I set my plugin to prerequisite on maven 4 (ok, it doesn't exists yet), but 
> the build just passed =/
> Sample attached



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to