[jira] Updated: (MNG-3765) Make plugin executions depend on packaging

["Brett Porter (JIRA)" <ji...@codehaus.org>]

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

Brett Porter updated MNG-3765:
------------------------------

    Fix Version/s: 3.x

certainly an interesting idea. This might also be more effectively handled using mixins.

> Make plugin  executions depend on packaging
> -------------------------------------------
>
>                 Key: MNG-3765
>                 URL: http://jira.codehaus.org/browse/MNG-3765
>             Project: Maven 2
>          Issue Type: New Feature
>          Components: Plugins and Lifecycle
>    Affects Versions: 2.0.9
>            Reporter: Karsten Tinnefeld
>             Fix For: 3.x
>
>
> Using plugin  executions, I can configure custom plugins to enter the maven lifecycles. That way, I may e.g. add functionality provided by the codehaus was6-maven-plugin to generate client stub classes or the like. In a multi-module enterprise project, I'd like to move the plugin configuration to a parent pom in order to give one proper configuration for a lot of ejb modules. The plugin, however, requires the configuration to be given in an ejb pom, in this case. Therefore, I'd like to have an option to configure (for all effective-poms inheriting from some master) that an executing comes into effect if and only if the packaging type is as specified (ejb for one case, ear for another).

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