geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Dillon (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMO-641) Compile fails using forked compiler when directory contains spaces
Date Thu, 14 Jun 2007 17:01:26 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jason Dillon closed GERONIMO-641.
---------------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: 1.x)
         Assignee: Jason Dillon

Fixed in 1.2 and 2.0, 1.1.x is dormant.

> Compile fails using forked compiler when directory contains spaces
> ------------------------------------------------------------------
>
>                 Key: GERONIMO-641
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-641
>             Project: Geronimo
>          Issue Type: Task
>          Components: buildsystem
>    Affects Versions: 1.0-M3
>         Environment: Windoze, but generic env applies
>            Reporter: Waimun Yeow
>            Assignee: Jason Dillon
>            Priority: Trivial
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message