You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brian Fox (JIRA)" <ji...@codehaus.org> on 2007/04/25 05:16:26 UTC

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

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

Brian Fox commented on MENFORCER-3:
-----------------------------------

You should be able to bind this in your pom by specifying the phase. Unfortunately, maven only allows a plugin to declare a single phase by default...that doesn't mean you can't add an execution for it though.

> 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