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

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

Github user josephw commented on the pull request:

    https://github.com/apache/maven/pull/51#issuecomment-138297080
  
    @jvanzyl although the original change was unconditional deprecation, I 
changed it after comments so the current language in the patch is intended to 
reflect that distinction:
    
    > For a plugin project, the minimum version of Maven required to use
    the resulting plugin.
    > For specifying the minimum version of Maven required to build a project, 
this element is <b>deprecated</b>.
    
    My intention here is to make clear that it's deprecated for *some* purposes.


> Site should tell 'prerequisites.maven is deprecated'
> ----------------------------------------------------
>
>                 Key: MNG-5297
>                 URL: https://issues.apache.org/jira/browse/MNG-5297
>             Project: Maven
>          Issue Type: Bug
>          Components: Sites & Reporting
>    Affects Versions: 3.0.4
>            Reporter: Kengo TODA
>            Priority: Minor
>
> MNG-4840 said 'enforcement of the build environment is left to the Maven 
> Enforcer Plugin'.
> http://jira.codehaus.org/browse/MNG-4840?focusedCommentId=253900&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-253900
> But currently, there is no 'deprecated' mark at Maven site. 
> http://maven.apache.org/ref/3.0.4/maven-model/maven.html#prerequisites
> I think site should has 'deprecated' mark like 'reports' element.



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

Reply via email to