geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevan Miller (JIRA)" <>
Subject [jira] Updated: (GERONIMO-641) Compile fails using forked compiler when directory contains spaces
Date Tue, 22 Nov 2005 23:23:41 GMT
     [ ]

Kevan Miller updated GERONIMO-641:

    Fix Version: 1.x
                     (was: 1.0)

I'm running Maven 1.0.2 and this is still a problem. However, I'm moving fix version to 1.x
(I'll sleep just fine...)

    [mkdir] Created dir: D:\test dir\geronimo\modules\j2ee-builder\target\test-ear14\test-ejb-jar\META-INF
    [copy] Copying 2 files to D:\test dir\geronimo\modules\j2ee-builder\target\test-ear14\test-ejb-jar\META-INF
    [javac] Compiling 20 source files to D:\test dir\geronimo\modules\j2ee-builder\target\test-ear14\test-ejb-jar
    [javac] javac: invalid flag: D:\test
    [javac] Usage: javac <options> <source files>
    [javac] where possible options include:
    [javac]   -g                        Generate all debugging info
    [javac]   -g:none                   Generate no debugging info
    [javac]   -g:{lines,vars,source}    Generate only some debugging info
    [javac]   -nowarn                   Generate no warnings
    [javac]   -verbose                  Output messages about what the compiler is doing
    [javac]   -deprecation              Output source locations where deprecated APIs are
    [javac]   -classpath <path>         Specify where to find user class files
    [javac]   -sourcepath <path>        Specify where to find input source files
    [javac]   -bootclasspath <path>     Override location of bootstrap class files
    [javac]   -extdirs <dirs>           Override location of installed extensions
    [javac]   -d <directory>            Specify where to place generated class files
    [javac]   -encoding <encoding>      Specify character encoding used by source files
    [javac]   -source <release>         Provide source compatibility with specified
    [javac]   -target <release>         Generate class files for specific VM version
    [javac]   -help                     Print a synopsis of standard options

File...... C:\Documents and Settings\Administrator\.maven\cache\maven-multiproject-plugin-1.3.1\plugin.jelly
Element... maven:reactor
Line...... 217
Column.... 9
Unable to obtain goal [default] -- D:\test dir\geronimo\modules\j2ee-builder\maven.xml:72:25:
<ant:javac> Compile failed
; see the compiler error output for details.
Total time: 3 minutes 43 seconds
Finished at: Tue Nov 22 18:12:52 EST 2005

> Compile fails using forked compiler when directory contains spaces
> ------------------------------------------------------------------
>          Key: GERONIMO-641
>          URL:
>      Project: Geronimo
>         Type: Task
>   Components: buildsystem
>     Versions: 1.0-M3
>  Environment: Windoze, but generic env applies
>     Reporter: Waimun Yeow
>     Priority: Trivial
>      Fix For: 1.x

> 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="${}/test-ejb-jar"
>             source="${maven.compile.source}"
>             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

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message