See my comments on the new Maven thread ...
On 1/10/06, Wendy Smoak <[EMAIL PROTECTED]> wrote: > On 1/10/06, Bill Dudney <[EMAIL PROTECTED]> wrote: > > > Ah the artifactId, is what is causing it... > > I really think we need a top level pom that is obviously a top level pom. > > > > What does everyone think about deleting 'build' and moving that pom into > > current? > > I wouldn't put a pom in current, though I can't come up with a > coherent reason why not. I don't use it, but ISTR complaints from > Eclipse users about that sort of structure. I'd have to see what IDEA > thinks of it before commenting further. :) > > Maven actually looks in the repository for the parent pom, so it > doesn't matter too much where it lives. You can use > <parent> > ... > <relativePath>../path/pom.xml</relativePath> > </parent> > to provide a hint. This lets Maven pick up local modifications to the > parent pom before it's installed in the repository. > > -- > Wendy >
