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

2017-02-23 Thread Stephen Connolly (JIRA)

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

Stephen Connolly updated MNG-6092:
--
Fix Version/s: (was: 3.5.0-alpha-2)

> 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, 3.5.0-alpha-1
>
>
> 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)


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

2017-02-23 Thread Stephen Connolly (JIRA)

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

Stephen Connolly updated MNG-6092:
--
Fix Version/s: 3.5.0-alpha-2
   3.5.0-alpha-1

> 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, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> 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)


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

2017-01-09 Thread Stephen Connolly (JIRA)

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

Stephen Connolly updated MNG-6092:
--
Fix Version/s: (was: 3.4.0)
   3.5.0

> 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
>
>
> 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)


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

2016-10-01 Thread Karl Heinz Marbaise (JIRA)

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

Karl Heinz Marbaise updated MNG-6092:
-
Summary: warn if prerequisites.maven is used for non-plugin projects  (was: 
warn if prerequisites.maven used for non-plugin projects)

> 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)