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

Paul Benedict updated MNG-3765:
-------------------------------

    Fix Version/s:     (was: Issues to be reviewed for 3.x)

> Make plugin  executions depend on packaging
> -------------------------------------------
>
>                 Key: MNG-3765
>                 URL: https://jira.codehaus.org/browse/MNG-3765
>             Project: Maven
>          Issue Type: New Feature
>          Components: Plugins and Lifecycle
>    Affects Versions: 2.0.9
>            Reporter: Karsten Tinnefeld
>
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)

Reply via email to