[GRADLE-1804] Allow to pass command line arguments to a task Created: 22/Sep/11 Updated: 10/Feb/17 Resolved: 10/Feb/17
Sometime we need to pass a variable number of command line arguments to a task. One obvious example being JavaExec type tasks, as we might want to pass arguments to the underlying program to run, via the args parameter.
The current ways are:
One idea is to have a flag indicating that beyond this point, the command line arguments belong to the task, no more to Gradle. Perhaps a -A flag (like "arguments"), or like in Unix shells, a double dash –
gradle -Pt=someClass run -A tvf -X -o="a dir" "file name with spaces"
One advantage to this form is that the shell will interpret itself the arguments with their own quoting (and escape) rules, Gradle will see them as a bunch of arguments to be fed into the task as an array (or whatever suitable collection) via some predefined name.
|Comment by ronan michaux [ 21/Feb/13 ]|
A little tip to pass command line ending args to a JavaExec task in Linux & bash environment.
JavaExec params are passed by a small temp file.
|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:
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.