I understood that modules were called from the parent. I was trying to understand the relationship in the other direction. It sounds like it consults the parent POM and inherits its attributes but does *not* build it. That's more of what I would expect ...
Sean On 1/5/06, Bill Dudney <[EMAIL PROTECTED]> wrote: > > On Jan 5, 2006, at 2:13 PM, Arvid Hülsebus wrote: > > > Sean Schofield wrote: > > > >> Does this mean that if you build the child, it asks the parent to > >> build? If so, then that is interesting (not a problem - just > >> unexpected.) > >> > > As far as I understand it Maven only builds "child" projects if the > > POM includes a module entry for that "child". In general it applies > > a goal on all included modules. These child modules won't even need > > a parent entry. Maven just changes into the directory with name in > > the module entry. > > > > The parent entry is more or less for inheriting common stuff. But > > it won't instruct Maven to build the parent. > > > > Sorry Sean, I missed that in my last response. My understanding and > experiences mirrors Arvid's. > > TTFN, > > -bd- > >
