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