On 15 November 2010 14:57, Bobby Bissett <bobby.bissett_at_oracle.com> wrote:
> I build with an empty Maven cache all the time, and it works for me. I'm not a maven expert, but I know what the maven experts ask. :) Can you tell us what version of maven you're using and what you have in your settings file. If it helps, I have this:
>
> hostname% mvn --version
> Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
Hi Bobby thanks for answering, I have this:
super_at_oem-desktop Mon Nov 15 03:52 PM ~
$ java -version
java version "1.6.0_22"
Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
Java HotSpot(TM) Server VM (build 17.1-b03, mixed mode)
super_at_oem-desktop Mon Nov 15 03:52 PM ~
$ mvn --version
Apache Maven 2.2.1 (rdebian-1)
Java version: 1.6.0_22
Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux" version: "2.6.32-25-generic" arch: "i386" Family: "unix"
My settings file points to my Nexus repo manager, so not so easy to
report here, but it does contain net/1, net/2 and glassfish repos,
along with a few others.
> I have no settings.xml file and an empty repo:
>
> hostname% find ~/.m2
> /Users/bobby/.m2
> /Users/bobby/.m2/repository
Now that is one bit I _don't_ understand, you have no cache at all?
Ah, perhaps you are using one in /tmp, in which case you may no longer
have the evidence that I seek ;)
It would be helpful if you could search in /tmp/m2 after a build and
see if my missing artifact is there.
> ...and it just built ok for me. Did you remember the "-Prelease-phase1" part?
Yes, I did that. The build got about half-way through before it
failed. I have just deleted the entire checkout & started again, and
have encountered exactly the same failure.
Ian.