Nevermind, I figured it out. For some reason I had M2_HOME in my
~/.mavenrc set and pointing to my 2.0.2 installation. Commented that
out and it works just fine now.
Rich
Richard Wallace wrote:
I tried to upgrade from version 2.0.2 to 2.0.3 because I've been
bumping into the problem where the <activeByDefault/> seems to be
ignored. So I untarred everything (I'm running Ubuntu Linux) and
tried to run mvn --version and here's what I get:
$ mvn --version
[INFO] Scanning for projects...
[INFO]
----------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
----------------------------------------------------------------------------
[INFO] Invalid task '"--version"': you must specify a valid lifecycle
phase, or a goal in the format plugin:goal or
pluginGroupId:pluginArtifactId:pluginVersion:goal
I really don't care if '--version' doesn't work, but if I try and do
anything, like mvn install, it does something similar:
$ mvn install
[INFO] Scanning for projects...
[INFO]
----------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
----------------------------------------------------------------------------
[INFO] Invalid task '"install"': you must specify a valid lifecycle
phase, or a goal in the format plugin:goal or
pluginGroupId:pluginArtifactId:pluginVersion:goal
Any idea what's going on?
Thanks,
Rich
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
