You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2017/03/29 20:49:41 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15947860#comment-15947860 ]
Hudson commented on MNG-6092:
-----------------------------
SUCCESS: Integrated in Jenkins build Tobago Trunk #837 (See [https://builds.apache.org/job/Tobago%20Trunk/837/])
removed prerequisites as this is only intended for maven-plugin projects but not for non maven-plugin projects. see also MNG-6092 (deki: [http://svn.apache.org/viewvc/?view=rev&rev=1789409])
* (edit) tobago-trunk/pom.xml
> 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.5.0-alpha-1, 3.5.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.15#6346)