> -----Original Message----- > From: Wayne Fay [mailto:wayne...@gmail.com] > Sent: Wednesday, December 19, 2012 10:09 AM > To: Maven Users List > Subject: Re: Proper fix for "non-resolvable" dependency in build server > > > 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
It would look like this: project-top [modules: project-parent, java-project-parent, war-project-parent, dataservice-build, dataserviceGUI] + project-parent + java-project-parent [parent: project-parent] + war-project-parent [parent: java-project-parent] + dataservice-build [modules: ../dataservice, ../dataservice-ear] + dataserviceGUI [parent: war-project-parent] + dataservice-ear [parent: project-parent] + dataservice [parent: war-project-parent] > 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. That is my intention. There is at least one artifact that I'll have to manually install to nexus (Oracle jdbc driver), but otherwise the intention is that it should build out of the box. However, I also want to allow for a couple of different checkout configurations. Some people will check out from "project-top" to build the entire project, but someone people will just be checking out the three parent poms and "dataserviceGUI", and some will need the three parents and "dataservice-build", "dataservice-ear", and "dataservice". I suppose that means that I can always depend on "../*-project-parent" to exist, so perhaps setting the values for "relativePath" could always work. > 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: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
