> I have a top-level aggregator pom that specifies several modules, but this pom > is not the parent of any module. I do use parent poms, but those parents are > in > peer directories, and I have blank "relativePath" elements in all poms.
This is most likely "wrong" and you should specify the proper relativePath. > The "java-project-parent" is one of the poms in the parent hierarchy. I have trouble following your email because I cannot "picture" the project layout. Can you reply with the basic layout in text form along with important details eg: project-parent [top-level aggregator, not the actual parent of anything below] + java-project-parent [parent of this and that] + this + that + notjava-project-parent [parent of another] + another etc I would guess that some usage of "mvn -N install" from the top would cure your problem. But that should not be necessary. You should be able to just run "mvn clean verify" from the top and everything should "just work" in a project that just got checked out of source code on a new machine that just installed Maven. If not, you are probably doing something wrong in your build somewhere. You may also benefit from reading Stephen Connolly's recent emails to this list in the thread "Recursive Maven considered harmful" especially the section starting with "You are doing Maven wrong if your entire build cannot work under the following incremental behaviors..." [timestamp on that email is Mon, 17 Dec 2012 11:36:42 +0000]. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
