[ http://jira.codehaus.org/browse/MNG-436?page=all ] Brett Porter closed MNG-436: ----------------------------
verified > implement plugin inheritance > ---------------------------- > > Key: MNG-436 > URL: http://jira.codehaus.org/browse/MNG-436 > Project: Maven 2 > Type: New Feature > Components: maven-core > Versions: 2.0-alpha-2 > Reporter: John Casey > Assignee: John Casey > Fix For: 2.0-alpha-3 > > > inherit all plugins that DO NOT have <inherit>false</inherit>. > For those INHERITED plugins that did not specify <inherit>true</inherit>, > check the inheritByDefault descriptor attribute to see whether the plugin > should be bound to the lifecycle. > so, the resulting lifecycle should contain: > 1. plugins defined in the local pom.xml > 2. plugins defined in an ancestor pom, with the <inherit>true</inherit> > specification > 3. plugins defined in an ancestor pom, without <inherit/> specified, but with > the inheritByDefault descriptor attribute set to "true". > NOTE: The same inheritance calculation will also take place at the goal level. > NOTE 2: In the MojoDescriptor, the inheritByDefault attribute can be set via > the @inheritByDefault "(true|false)" annotation. > NOTE 3: Currently there is no way to specify the inheritByDefault attribute > for the plugin level, without writing the plugin.xml by hand. This is because > a plugin is a logical construct, and when the descriptor is generated it is > really just an aggregation of all the mojo-level annotations plus some > information from the plugin's POM. -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
