You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Laurent Sellin (JIRA)" <ji...@codehaus.org> on 2005/05/20 16:59:57 UTC

[jira] Commented: (MPJAVA-4) Compile fails using forked compiler when directory contains spaces

     [ http://jira.codehaus.org/browse/MPJAVA-4?page=comments#action_39413 ]
     
Laurent Sellin commented on MPJAVA-4:
-------------------------------------

As indicated in the external reference, setting maven.compile.fork=no (eg. in build.properties) seems to be a good workaround for the moment if you use file path with spaces under windows...
I am looking forward to see this solved, as it is very blocking (for someone new to maven it is not easy to solve).


> Compile fails using forked compiler when directory contains spaces
> ------------------------------------------------------------------
>
>          Key: MPJAVA-4
>          URL: http://jira.codehaus.org/browse/MPJAVA-4
>      Project: maven-java-plugin
>         Type: Bug
>  Environment: Windows NT
>     Reporter: Deleted User with username (Firewater)

>
>
> Running the java:compile goal usually runs fine.  However, if you want to fork it to use another java compiler, the compile fails since javac treats the first section of the source directory as an argument.
> Thus a project under 'c:\project\my project' fails with the error 'javac: invalid argument: c:\project\my'
> I tried to look and see what's causing this, but couldn't figure out why the directory was treated differently when forked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org