You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2005/08/30 23:03:04 UTC
[jira] Updated: (GERONIMO-641) Compile fails using forked compiler when directory contains spaces
[ http://issues.apache.org/jira/browse/GERONIMO-641?page=all ]
Aaron Mulder updated GERONIMO-641:
----------------------------------
Fix Version: 1.0-M5
Description:
Using forked compiler in <ant:javac> causes compile to fail. The following is encountered during the build of j2ee-builder/maven.xml.
/***********************
setupEar:
[javac] Compiling 20 source files to C:\Documents and Settings\Geronimo Team\My
Documents\test\geronimo\modules\j2ee-builder\target\test-ear14\test-ejb-jar
[javac] javac: invalid flag: C:\Documents
[javac] Usage: javac <options> <source files>
*************/
The maven file:
<ant:javac srcdir="${ear.src.base.dir}/test-ejb-jar"
destdir="${ear.target.base.dir}/test-ejb-jar"
source="${maven.compile.source}"
target="${maven.compile.target}"
debug="on"
fork="true">
<!--
changing fork="false" works
//I generally use paths without spaces in windows, but I found this error because I was test compiling it in "documents and settings"
-->
Comment by Brett Porter [07/May/04 08:54 PM]
looks like we need to wait for the Ant upgrade in future versions of Maven
This is an issue with maven. See http://jira.codehaus.org/browse/MPJAVA-4
was:
Using forked compiler in <ant:javac> causes compile to fail. The following is encountered during the build of j2ee-builder/maven.xml.
/***********************
setupEar:
[javac] Compiling 20 source files to C:\Documents and Settings\Geronimo Team\My
Documents\test\geronimo\modules\j2ee-builder\target\test-ear14\test-ejb-jar
[javac] javac: invalid flag: C:\Documents
[javac] Usage: javac <options> <source files>
*************/
The maven file:
<ant:javac srcdir="${ear.src.base.dir}/test-ejb-jar"
destdir="${ear.target.base.dir}/test-ejb-jar"
source="${maven.compile.source}"
target="${maven.compile.target}"
debug="on"
fork="true">
<!--
changing fork="false" works
//I generally use paths without spaces in windows, but I found this error because I was test compiling it in "documents and settings"
-->
Comment by Brett Porter [07/May/04 08:54 PM]
looks like we need to wait for the Ant upgrade in future versions of Maven
This is an issue with maven. See http://jira.codehaus.org/browse/MPJAVA-4
Can someone with a Windows machine check whether our build fails if the source directory has spaces in the name? If not, I think this issue should be closed. Thanks.
> Compile fails using forked compiler when directory contains spaces
> ------------------------------------------------------------------
>
> Key: GERONIMO-641
> URL: http://issues.apache.org/jira/browse/GERONIMO-641
> Project: Geronimo
> Type: Task
> Components: buildsystem
> Versions: 1.0-M3
> Environment: Windoze, but generic env applies
> Reporter: Waimun Yeow
> Priority: Trivial
> Fix For: 1.0-M5
>
> Using forked compiler in <ant:javac> causes compile to fail. The following is encountered during the build of j2ee-builder/maven.xml.
> /***********************
> setupEar:
> [javac] Compiling 20 source files to C:\Documents and Settings\Geronimo Team\My
> Documents\test\geronimo\modules\j2ee-builder\target\test-ear14\test-ejb-jar
> [javac] javac: invalid flag: C:\Documents
> [javac] Usage: javac <options> <source files>
> *************/
> The maven file:
> <ant:javac srcdir="${ear.src.base.dir}/test-ejb-jar"
> destdir="${ear.target.base.dir}/test-ejb-jar"
> source="${maven.compile.source}"
> target="${maven.compile.target}"
> debug="on"
> fork="true">
> <!--
> changing fork="false" works
> //I generally use paths without spaces in windows, but I found this error because I was test compiling it in "documents and settings"
> -->
> Comment by Brett Porter [07/May/04 08:54 PM]
> looks like we need to wait for the Ant upgrade in future versions of Maven
> This is an issue with maven. See http://jira.codehaus.org/browse/MPJAVA-4
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira