Hy Markus, thank you for your quick answer. On 15 May 2006 at 16:17, Markus Reinhardt wrote: > > <relativePath>../pom.xml</relativePath> > > You may try putting relativePath in here. This prevents maven from looking > for the POM in any > repository. Even the relativePath element doesn't work in the b subdirectory. > > Another thing that worked for me ist to run 'mvn install' on all projects > with > <packaging>pom</packaging>. This puts the POM in your local repo, where it is > found by maven > during the build of the submodules. > I have some profiles in the top level pom. In the profiles I have version numbers for different releases of the subprojects (b.a, b.b, ...). There I use the version numbers as pom.versionId or dependency versions.
And maven doesn't replace these values (provided in a/pom.xml) in the subproject b.a. and so b.a/pom.xml fails to find the right poms from the repo. But if I cd to a/b/b.a all values get resolved ... So it seems to be a bug in maven?! regards, carsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
