[GRADLE-1577] JavaExec task doesn't seem to handle spaces in the executable path or in classpath. Created: 27/May/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-3
Fix Version/s: None

Type: Bug
Reporter: Jason Hatton Assignee: Unassigned
Resolution: Won't Fix Votes: 0


I have the following JavaExec task set up:

task(gwtCompile, dependsOn: classes, type: JavaExec)

{ main = 'com.google.gwt.dev.Compiler' jvmArgs = ['-Xmx512M'] classpath files(file('src')) classpath sourceSets.main.runtimeClasspath args "-war $buildDir" args '-logLevel INFO' args 'com.acme.application.GwtModule' }

The error I get from running this through the JavaExec task is:

Unknown argument: -war C:\application\client\build

I figured out the command line wasn't getting executed correctly because of spaces in the path to the java.exe (e.g. C:\Program Files\Java\jdk1.6.0_20\bin) and where the jars are in the gradle cache under C:\Documents and Settings

I printed out the command line from gradle using below:

gwtCompile.doFirst {
println "command line: ${gwtCompile.commandLine}"
println "executable: ${gwtCompile.executable}"

Dumped this into a Windows bat file and double quoted around the paths that had spaces and was able to execute the task as I expected it to work.


Comment by Jason Hatton [ 28/May/11 ]

I made a mistake on the environment. I am running this on Windows XP.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 11:59:05 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.