Steve determined the cause of the build failures to be a Maven version
mismatch - I was on 2.0.2 and he was 2.0.4 (latest release). I upgraded
and the problems went away. I have updated the POM to require 2.0.4, which
means that you need to upgrade too. ;)
Upgrading to 2.0.4 was pretty painless. Assuming you have a directory
called {$apache_software}/maven2.0.2 and a /conf/settings.xml file that
points to your desired local repository, you have to:
1. download maven 2.0.4
2. copy it to {$apache_software}/maven2.0.4
3. copy your repository location into the new /conf/settings.xml file
4. change the M2_HOME environment variable to reference
{$apache_software}/maven2.0.4 instead of {$apache_software}/maven2.0.2
5. if you're running maven from within eclipse: I had to restart eclipse
to get its console component to reload the current env. variables.
your repository remains the same, so you won't have to re-download
anything or re-initialize the basic repository items.
Dan
Dan Jemiolo
IBM Corporation
Research Triangle Park, NC
+++ I'm an engineer. I make slides that people can't read. Sometimes I eat
donuts. +++
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
