Even if I properly escape spaces in a path at the shell level, Maven
seems to attempt to re-tokenize the command parameters. For instance,
on Unix, the following seems as if it should run the compile goal
with a "foo" parameter valued "bar baz":
$ mvn compile "-Dfoo=bar baz"
But in fact, it fails, complaining that "baz" is an invalid task:
[INFO] Scanning for projects...
[INFO]
------------------------------------------------------------------------
----
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
----
[INFO] Invalid task 'baz': you must specify a valid lifecycle
phase, or a goal in the format plugin:goal or
pluginGroupId:pluginArtifactId:pluginVersion:goal
[INFO]
------------------------------------------------------------------------
----
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
----
[INFO] Total time: < 1 second
[INFO] Finished at: Wed Mar 29 15:21:01 EST 2006
[INFO] Final Memory: 1M/2M
[INFO]
------------------------------------------------------------------------
----
This looks very much like a bug. Is this intended behavior? I was
merely trying to run
mvn deploy:deploy-file "-Dfile=[path that happened to include
spaces]" ...
— G
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
