RE: Resolving parent pom from the filesystem

[ljnelson <lj...@gmail.com>]

Yanko, Curtis wrote:
> 
> 
> It *always* looks up a level for a pom. This is why I would only use
> that *up-a-level* pom for aggregation and not inheritance stuff. For
> that we make the parentpom project at the module level and *build* it
> (install or deploy) like any other project.
> 
> 

Oddly enough, so do we.  Sort of.  Let me explain.

Using my example from my prior email, C's parent, B, is a sibling to it on
the filesystem.  B's parent, A, is indeed a level up.

Now in the case where we were getting burned, C was checked out to disk, B
was not, and A was checked out to disk but stale with respect to the VC
system.

I would think in such a case it would be impossible for Maven to figure out
that--running from a build invoked in C's directory--A should be used from
the filesystem.  Let's follow the ball:

C's pom needs its parent resolved.  Maven has no choice but to go to the
repository, since B is not checked out.
B's pom needs its parent resolved.  B's pom that's being read is sourced
from the repo.
We are seeing that somehow A--B's parent--is being resolved from the
filesystem (mvn help:effective-pom shows this).  But how?

L
-- 
View this message in context: http://maven.40175.n5.nabble.com/Resolving-parent-pom-from-the-filesystem-tp3286818p3287671.html
Sent from the Maven - Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org