> Solution: > > - point MAVEN_HOME to maven-1.1-beta2 > - modify PATH to point the 'bin' folder of Maven 1.1 beta 2 > > Remark : if you do the first, but not the second, then you'll get the > error you indicated. What is confusing > however, is that you see '1.1-beta-2' in the Maven logo, despite the > fact that your configuration still > partially points to Maven-1.0.2.
The problem was even more subtle than that. Apparently when using VNC, creating a new xterm doesn't reset all the environment variables. So even though I changed MAVEN_HOME in my .bashrc and my PATH had PATH = MAVEN_HOME + PATH in it, I ended up with a PATH that had maven 1.1 in it and afterwards maven 1.0. This still would have worked if it were not for the fact that unzipping Maven 1.1 resulted in a maven script that was not executable, thus the shell found the maven script in the older 1.0 directory which was unknowingly in my path!!! I lost a lot of time figuring all that out. I agree with Brett, it'd be worth adding a check to see if multiple maven versions are in the path and give a warning message. Because it was very strange to have the script run from the maven 1.0 directory yet display 1.1-beta2 on the terminal!!! Thanks for the help, I wouldn't have figured this out myself. -Michael -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
