> -----Original Message-----
> From: KARR, DAVID
> Sent: Tuesday, December 18, 2012 7:26 PM
> To: Maven Users List
> Subject: Proper fix for "non-resolvable" dependency in build server
> 
> I have a project that is building fine on my laptop.  Today I started
> to set up the build for this on our Bamboo server.  Everything is
> checked in.  Both my laptop and the build server are using Maven 3.0.4.
> 
> I have a top-level aggregator pom that specifies several modules, but
> this pom is not the parent of any module.  I do use parent poms, but
> those parents are in peer directories, and I have blank "relativePath"
> elements in all poms.
> 
> In the Bamboo build of the top-level aggregator POM, I see several
> errors like this:
> 
> [ERROR]   The project com.example.cde:java-project-parent:1.0.1
> (/volatile/bamboo/bamboo3.4.3_data/xml-data/build-dir/FOO-BUILD-
> JOB1/java-project-parent/pom.xml) has 1 error
> 18-Dec-2012 16:40:21  [ERROR]     Non-resolvable parent POM: Failure
> to find com.example.cde:project-parent:pom:1.0.0 in
> http://hostname.net:8081/nexus/content/groups/stuff was cached in the
> local repository, resolution will not be reattempted until the update
> interval of nexus has elapsed or updates are forced and
> 'parent.relativePath' points at no local POM @ line 6, column 11 ->
> [Help 2]

Note that just before these lines in the log, I also see this:

Downloading: 
http://hostname.net:8081/nexus/content/groups/stuff/com/example/cde/project-parent/1.0.0/project-parent-1.0.0.pom
Downloading: 
http://hostname.net:8081/nexus/content/groups/stuff/com/example/cde/java-project-parent/1.0.1/java-project-parent-1.0.1.pom
Downloading: 
http://hostname.net:8081/nexus/content/groups/stuff/com/example/cde/war-project-parent/1.0.0/war-project-parent-1.0.0.pom

I'm confused.  It downloads the pom, apparently to the local repository, and 
then claims that it can't find it.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to