I just spent the past hour attempting to install Maven 1.0.2 in order to get some HtmlUnit work done.
Lesson the first: don’t point your JAVA_HOME environment variable to a path which includes spaces. This was a good rule of thumb back in 1997, but come on! Ten years later, and we’re still dealing with these issues? The Maven batch file is full of double-quoted variables and values, but apparently it’s just an effort to instill a false sense of security in unwary developers.
Lesson the second: do not, under any circumstances, add a trailing slash to your MAVEN_HOME environment variable. Doing so (ie, using “C:\java\maven-1.0.2\” instead of “C:\java\maven-1.0.2″) will cause Maven to throw the Java usage message at you, instead of doing something useful like, say, compiling your project.
It’s too bad that Mergere seems to be having some trouble. Both versions of Maven could really use the polish that comes with a professional [read: for money] operation a la JBoss…
UPDATE: Enter Sonatype!
