So, does anyone need an test case of this on a JIRA? On Fri, Mar 12, 2010 at 7:53 AM, Brian Fox <[email protected]> wrote:
> If the plugin is mentioned _at all_ even just group/artifact, then the > pluginManagement will kick in. This is how it works now. It should be > that you have to mention the executionId you want to inherit instead > of just assuming all of them. > > On Thu, Mar 11, 2010 at 10:37 PM, Benson Margulies > <[email protected]> wrote: > > Here, let me sketch this out... > > > > <build> > > <pluginManagement> > > <plugins> > > <plugin> > > <groupId>g</groupId> > > <artifactId>a</artifactId> > > <version>v</version> > > <executions> > > <execution> > > <id>ego</id> > > <goals><goal>g1</goal></goals> > > </execution> > > </executions> > > </plugin> > > </plugins> > > </pluginManagement> > > <plugins> > > <plugin> > > <groupId>g</groupId> > > <artifactId>a</artifactId> > > <version>v</version> > > <executions> > > <execution> > > <id>super</id> > > <goals><goal>g2</goal></goals> > > </execution> > > </executions> > > </plugin> > > </plugins> > > </build> > > > > If this is in the parent, and the child mentions g2 in it's > //build/plugins, > > the child runs BOTH, even if it never mentions g1 in its own > //build/plugins > > (xpath) section. > > > > > > On Thu, Mar 11, 2010 at 10:24 PM, Brian Fox <[email protected]> wrote: > > > >> If the execution is mentioned in the parent plugin section, it's > >> inherited by the child, so yes it would run. If you don't want this, > >> then the parent should have the configuration in pluginManagement > >> (only) and then the child mentions the plugin in the plugins section. > >> > >> On Thu, Mar 11, 2010 at 1:12 PM, Anders Hammar <[email protected]> > wrote: > >> > I think I need to see a project to tell if I think it's wrong or not. > >> What I > >> > think you should start with is trying it with Maven 3.0-alpha-6 and > see > >> if > >> > it the same behavior. Many incorrect things in Maven 2 has been fixed > in > >> 3. > >> > > >> > /Anders > >> > > >> > On Thu, Mar 11, 2010 at 17:05, Benson Margulies < > [email protected] > >> >wrote: > >> > > >> >> Anders, > >> >> > >> >> If this sounds wrong to you, I'll put the effort into a test project. > >> >> > >> >> --benson > >> >> > >> >> > >> >> On Thu, Mar 11, 2010 at 10:43 AM, Anders Hammar <[email protected]> > >> wrote: > >> >> > >> >> > Have you tested with Maven-3.0-alpha-6? > >> >> > In either case, a test project to reproduce this would help. If you > >> think > >> >> > it's wrong, submit a jira with that project attached. > >> >> > > >> >> > /Anderfs > >> >> > > >> >> > On Thu, Mar 11, 2010 at 16:36, Benson Margulies < > >> [email protected] > >> >> > >wrote: > >> >> > > >> >> > > As an additional hint, and possible explanation: > >> >> > > > >> >> > > I have a project with multiple mojos in it. In the area where I'm > >> >> having > >> >> > > the > >> >> > > problem, I've got one of them specified in build/plugins in the > >> parent > >> >> > > project, and the other specified in > build/pluginManagement/plugins. > >> I > >> >> > can't > >> >> > > help wondering if there some sort of leakage here, or that the > >> entire > >> >> > > plugin, not the goal, is what gets managed. > >> >> > > > >> >> > > On Thu, Mar 11, 2010 at 10:25 AM, Benson Margulies < > >> >> > [email protected] > >> >> > > >wrote: > >> >> > > > >> >> > > > In the parent project, I declare a plugin in pluginManagement. > >> >> > > > > >> >> > > > In one of the children, I do \not/ reference it at all. Yet, > >> >> > > > help:effective-pom shows it in the build/plugins, and it's > trying > >> to > >> >> > run. > >> >> > > > > >> >> > > > Any suggestions? > >> >> > > > > >> >> > > > >> >> > > >> >> > >> > > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
