[jira] Closed: (MENFORCER-3) enforcer plugin should be bound to the 'clean' lifecycle in addition to the 'default' lifecycle

["Ian Springer (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MENFORCER-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ian Springer closed MENFORCER-3.
--------------------------------

    Resolution: Won't Fix

Maven does no allow plugins to bind to more than one phase, even if the phases are in different lifecycles.


> enforcer plugin should be bound to the 'clean' lifecycle in addition to the 'default' lifecycle
> -----------------------------------------------------------------------------------------------
>
>                 Key: MENFORCER-3
>                 URL: http://jira.codehaus.org/browse/MENFORCER-3
>             Project: Maven 2.x Enforcer Plugin
>          Issue Type: Bug
>          Components: Plugin
>    Affects Versions: 1.0-alpha-1
>            Reporter: Ian Springer
>            Assignee: Brian Fox
>
> I think it makes sense for the enforcer plugin to also be bound to the 'pre-clean' phase of the 'clean' lifecycle, so that when I just run 'mvn clean', the enforcer plugin will still check the Maven, JDK, etc. versions.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira