But if I do the compile in a/b/b.a it works w/o install. I think it should work - my use case is: large structure with a lot of projects - I modify something in a subproject, add something to the profile in the top project - and I cant do a compile/package in the subproject for testing - and I can't do an install in the top project because one of my subprojects fails. (I have to migrate from ant to Maven 2 ...) My workaround is, to make the changes, put the parent pom via copy in the repo and so I can use the new profile variables in my subprojects, but my hope was, that the poms get resolved in subdir a/b as they get resolved in subdir a/b/b.a
regards, carsten On 18 May 2006 at 13:37, Trygve Laugstøl wrote: > Carsten Karkola wrote: > > Hi, > > > > I've created the following directory layout > > > > /a - pom.xml > > /b - pom.xml > > - /b.a -pom.xml > > > > My executions: > > $> cd ~/a > > $> mvn compile > > [INFO] BUILD SUCCESSFUL > > You have to do 'mvn install' to install the pom into the repository. If > not Maven doesn't have any places to find the parent pom. > > -- > Trygve > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
