[
https://issues.apache.org/jira/browse/MNG-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14733689#comment-14733689
]
ASF GitHub Bot commented on MNG-5297:
-------------------------------------
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/51#issuecomment-138295450
No. The enforcer plugin is for build-time enforcement. The <prerequisite/>
element is for runtime enforcement. We certainly don't want to have to inspect
the any plugin configuration elements to help Maven know that the current
environment won't run the plugin. Also, if we ever get around to having the
build vs consumption POM this information would not be available at all.
> 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)