maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Kolotyluk <>
Subject Re: Referencing a parent POM without relativePath
Date Fri, 23 Nov 2012 20:22:58 GMT
I tried putting <relativePath/> in my POM, but it does not fix things.


I still get

C:\Users\Eric\workspace\tree-combo-box>mvn clean
[INFO] Scanning for projects...
[WARNING] Could not transfer metadata 
com:kodak:0.0.11-SNAPSHOT/maven-metadata.xml from/to nexus 
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   The project 
(C:\Users\Eric\workspace\tree-combo-box\pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM: Could not transfer artifact 
com:kodak:pom:0.0.11-SNAPSHOT from/to nexus 
( and 'parent.relativePath' points at no local POM 
@ line 9, column 11: Unknown host -> [Help 2]
[ERROR] To see the full stack trace of the errors, re-run Maven with the 
-e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] For more information about the errors and possible solutions, 
please read the following articles:
[ERROR] [Help 1]
[ERROR] [Help 2]

It looks like Maven wants to download the Corporate POM because it sees 
it in Nexus, but craps out because it does not like the Project POM. 
Maven seems pretty certain that it wants parent.relativePath to point to 
a local POM.

Is there a <userFriendly>true</userFriendly> switch I can turn on 
somewhere in Maven ;-)

Cheers, Eric

On 2012-11-23 9:05 AM, Laird Nelson wrote:
> On Fri, Nov 23, 2012 at 11:22 AM, Benson Margulies <>wrote:
>> You just name the G/A/V and no relativePath, and Maven will download
>> just as it would a dependency.
> Well, not exactly; if there is no <relativePath> element present, then
> Maven behaves as though <relativePath>../pom.xml</relativePath> were
> specified.  If that file is a working copy that has not been refreshed from
> the SCM, then problems can ensue.
> I recall that someone mentioned specifying a relative path like this:
> <relativePath/>
> ...and that that was the only way to force Maven to truly resolve the pom
> from the repository, but I don't know if this is in fact true.
> Best,
> Laird

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

View raw message