I can't reproduce this with Gradle 1.6.

Here's what I tried:

apply plugin: "application"
apply plugin: "groovy"

mainClassName = "Main"

repositories {
mavenCentral()
}

dependencies {
groovy localGroovy()
}

run {
args = [ "the
apply plugin: "application"
apply plugin: "groovy"

mainClassName = "Main"

repositories {
mavenCentral()
}

dependencies {
groovy localGroovy()
}

run {
args = [ "the \"argu\" ment" ]
}
quot;argu
apply plugin: "application"
apply plugin: "groovy"

mainClassName = "Main"

repositories {
mavenCentral()
}

dependencies {
groovy localGroovy()
}

run {
args = [ "the \"argu\" ment" ]
}
quot; ment" ]
}

Then run: `gradle run`.

The arg is quoted.

I still see this with gradle 1.6 with the `run` task as well as with my example of `JavaExec`.

% gradle run
:compileJava UP-TO-DATE
:compileGroovy UP-TO-DATE
:processResources UP-TO-DATE
:classes UP-TO-DATE
:run
the argu ment

BUILD SUCCESSFUL

Here my gradle info:

------------------------------------------------------------
Gradle 1.6
------------------------------------------------------------

Gradle build time: Dienstag, 7. Mai 2013 09:12 Uhr UTC
Groovy: 1.8.6
Ant: Apache Ant(TM) version 1.8.4 compiled on May 22 2012
Ivy: 2.2.0
JVM: 1.7.0_04 (Oracle Corporation 23.0-b21)
OS: Windows 7 6.1 amd64

Ah, Windows... the great destroyer of quotes. I'll dig a little deeper. There are some long standing JDK (ProcessBuilder and friends) bugs in this area that I think are biting here.

Sorry. I should have made this more explicit. I wrote it in the heading, though. :-|

Yeah, my fault for not picking it up the first time.

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!

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.