Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Date: Thu, 25 Jul 2013 15:19:05 -0500 (CDT)
From: "Mirko Friedenhagen (JIRA)" <jira@codehaus.org>
To: issues@maven.apache.org
Message-ID: 
 <JIRA.147397.1373489981678.9760.1374783545558@codehaus01.managed.contegix.com>
In-Reply-To: <JIRA.147397.1373489981678@codehaus01.managed.contegix.com>
References: <JIRA.147397.1373489981678@codehaus01.managed.contegix.com>
Subject: [jira] (MENFORCER-159) Add goal recommend which will only warn but
 never fail a build
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


    [ https://jira.codehaus.org/browse/MENFORCER-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329517#comment-329517 ] 

Mirko Friedenhagen commented on MENFORCER-159:
----------------------------------------------

[~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 goal recommend which will only warn but never fail a build
> --------------------------------------------------------------
>
>                 Key: MENFORCER-159
>                 URL: https://jira.codehaus.org/browse/MENFORCER-159
>             Project: Maven 2.x Enforcer Plugin
>          Issue Type: New Feature
>          Components: Plugin
>    Affects Versions: 1.3
>            Reporter: Mirko Friedenhagen
>            Assignee: Olivier Lamy
>             Fix For: 2.0
>
>         Attachments: recommend-mojo.patch
>
>
> In our company's parent POM we define a lot of rules, some of which are controversial or may not be easily fulfilled. The patch I attach defines a new goal "recommend" which will always warn but never fail. It's configuration is done by a new element {{recommendations}} which just holds a sequence of rules.
> I extracted most of EnforceMojo to AbstractEnforceMojo to avoid code duplication. I added an invoker test and all tests ran successfully.
> See https://github.com/apache/maven-enforcer/pull/4 as well for easier review.

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