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

[ji...@codehaus.org]

The following comment has been added to this issue:

     Author: dion gillard
    Created: Wed, 24 Sep 2003 11:48 PM
       Body:
This is definitely a bug in the Ant javac task:

    [javac] [DEBUG] Execute:Java13CommandLauncher: Executing 'C:\j2sdk1.4.2_01\bin\javac.exe' with arguments:
'-d'
'C:\Temp\test\my maven\target\classes'
'-classpath'
'C:\Temp\test\my maven\target\classes;C:\temp\test\maven-repo-local\dom4j\jars\dom4j-1.4.jar;C:\temp\test\maven-repo-local\ant\jars\ant
-1.5.3-1.jar;C:\temp\test\maven-repo-local\ant\jars\ant-optional-1.5.3-1.jar;C:\temp\test\maven-repo-local\commons-betwixt\jars\commons
-betwixt-1.0-beta-1.20030111.103454.jar;C:\temp\test\maven-repo-local\commons-digester\jars\commons-digester-1.4.1.jar;C:\temp\test\mav
en-repo-local\commons-jelly\jars\commons-jelly-20030902.160215.jar;C:\temp\test\maven-repo-local\commons-jelly\jars\commons-jelly-tags-
ant-20030625.032346.jar;C:\temp\test\maven-repo-local\commons-jelly\jars\commons-jelly-tags-define-20030211.142932.jar;C:\temp\test\mav
en-repo-local\commons-jelly\jars\commons-jelly-tags-util-20030211.141939.jar;C:\temp\test\maven-repo-local\commons-graph\jars\commons-g
raph-0.8.1.jar;C:\temp\test\maven-repo-local\commons-jexl\jars\commons-jexl-1.0-beta-1.jar;C:\temp\test\maven-repo-local\commons-loggin
g\jars\commons-logging-1.0.1.jar;C:\temp\test\maven-repo-local\werkz\jars\werkz-1.0-beta-10.jar;C:\temp\test\maven-repo-local\commons-b
eanutils\jars\commons-beanutils-1.6.1.jar;C:\temp\test\maven-repo-local\commons-cli\jars\commons-cli-1.0-beta-2.jar;C:\temp\test\maven-
repo-local\commons-collections\jars\commons-collections-2.1.jar;C:\temp\test\maven-repo-local\commons-grant\jars\commons-grant-1.0-beta
-4.jar;C:\temp\test\maven-repo-local\commons-io\jars\commons-io-20030203.000550.jar;C:\temp\test\maven-repo-local\commons-lang\jars\com
mons-lang-1.0-b1.1.jar;C:\temp\test\maven-repo-local\forehead\jars\forehead-1.0-beta-5.jar;C:\temp\test\maven-repo-local\log4j\jars\log
4j-1.2.8.jar;C:\temp\test\maven-repo-local\which\jars\which-1.0.jar;C:\temp\test\maven-repo-local\xml-apis\jars\xml-apis-1.0.b2.jar;C:\
temp\test\maven-repo-local\xerces\jars\xerces-2.4.0.jar;C:\temp\test\maven-repo-local\xpp3\jars\xpp3-1.1.2a.jar;C:\temp\test\maven-repo
-local\plexus\jars\plexus-0.6.jar;C:\program files\maven\lib\forehead-1.0-beta-5.jar'
'-sourcepath'
'C:\Temp\test\my maven\src\java'
'-target'
'1.1'
'-g'
'@C:\Temp\test\my maven\files71809371'

The ' characters around the executable and arguments are
not part of the command.

    [javac] javac: invalid flag: C:\Temp\test\my
    [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 used
    [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 release
    [javac]   -target <release>         Generate class files for specific VM version
    [javac]   -help                     Print a synopsis of standard options
    [javac]

BUILD FAILED
---------------------------------------------------------------------
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-682


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-682
    Summary: Compile fails using forked compiler when directory contains spaces
       Type: Bug

     Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

    Project: maven
 Components: 
             plugin-java
   Fix Fors:
             1.0-final
   Versions:
             1.0-beta-10

   Assignee: 
   Reporter: Michael Brown

    Created: Thu, 14 Aug 2003 9:22 AM
    Updated: Fri, 15 Aug 2003 4:59 AM
Environment: Windows NT

Description:
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.


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report 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