[
https://jira.codehaus.org/browse/MENFORCER-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329518#comment-329518
]
Mirko Friedenhagen commented on MENFORCER-160:
----------------------------------------------
[~rfscholte], [~olamy]: Now we have the situation, that both MENFORCER-159 and
MENFORCER-160 are merged. I think we either should levels as outlined in
MENFORCER-160 or the additional goal as contributed in MENFORCER-159. Having
both seems to be confusing :-). What about discussing which approach to choose
on the developer's list?
> Add levels ERROR and WARN to enforcer rules
> -------------------------------------------
>
> Key: MENFORCER-160
> URL: https://jira.codehaus.org/browse/MENFORCER-160
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Bug
> Components: Plugin, Rule API, Standard Rules
> Affects Versions: 1.3.1
> Reporter: Mirko Friedenhagen
> Assignee: Olivier Lamy
> Fix For: 2.0
>
> Attachments: enable-level.patch
>
>
> As suggested in MENFORCER-159, it would be more feasible just have one goal
> but be able to differentiate via a level between rules which should fail the
> build and ones which only warn. I tried to be backwards compatible.
> See https://github.com/apache/maven-enforcer/pull/5 as well, sample
> configuration for WARN can be seen at
> https://github.com/mfriedenhagen/maven-enforcer/blob/6482333e64e67031e19cb5b928d5ad2ce896f38a/maven-enforcer-plugin/src/it/projects/always-fail-warn/pom.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
