maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yanko, Curtis" <>
Subject RE: Resolving parent pom from the filesystem
Date Tue, 30 Nov 2010 22:35:41 GMT

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.

Curt Yanko | Continuous Integration Services | UnitedHealth Group IT 
Making IT Happen, one build at a time, 600 times a day

> -----Original Message-----
> From: Laird Nelson [] 
> Sent: Tuesday, November 30, 2010 4:29 PM
> To:
> Subject: Resolving parent pom from the filesystem
> Is there a checklist in the Maven documentation somewhere 
> that definitively lists the conditions under which Maven 
> 2.2.1 (or 3.0) will resolve pom inheritance from the 
> filesystem rather than from the (local) repository?
> We have a situation where A is the root pom, and B and C are 
> two of its modules.  C is parented by B, and B is parented by A.
> None of these files has a <relativePath> element.  This is on purpose.
> In one developer's working area, she happens to have A 
> checked out, and it's stale.  B is not checked out.  C is checked out.
> When she runs mvn -U clean install on C, B's pom is obviously 
> resolved from the local repository (since it doesn't exist 
> anywhere on disk in her working area).  But surprisingly, mvn 
> help:effective-pom shows that A is being resolved from the 
> local filesystem.
> I thought that without a <relativePath> element this would 
> never happen.
> Clearly I was wrong.
> Any pointers are gratefully welcomed.
> Best,
> Laird

This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message