You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Karl Heinz Marbaise (JIRA)" <ji...@apache.org> on 2016/10/01 15:07:20 UTC

[jira] [Closed] (MNG-6092) warn if prerequisites.maven is used for non-plugin projects

     [ https://issues.apache.org/jira/browse/MNG-6092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Heinz Marbaise closed MNG-6092.
------------------------------------
    Resolution: Fixed

Done in [c10d813c69818a81a0b202b7bc48533db83e6e96|https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commitdiff;h=c10d813c69818a81a0b202b7bc48533db83e6e96]

> warn if prerequisites.maven is used for non-plugin projects
> -----------------------------------------------------------
>
>                 Key: MNG-6092
>                 URL: https://issues.apache.org/jira/browse/MNG-6092
>             Project: Maven
>          Issue Type: Wish
>          Components: core
>    Affects Versions: 3.3.9
>            Reporter: Hervé Boutemy
>            Assignee: Karl Heinz Marbaise
>             Fix For: 3.4.0
>
>
> as seen in MNG'4840 and documented in MNG-5297, in Maven 3, prerequisites.maven has a meaning for plugin projects: defining this for non-plugins projects makes feel that it will be checked like it was done in Maven 2, but this is not the case.
> Adding a warning could help people avoid this habit taken with Maven 2



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)