155

I have a Java application that runs with a custom gradle task and the application requires some arguments upon being invoked. These are:

programName ( string | -f filename | -d key | -h)
Options:
    string         Message to be used.
    -d key         Use default messages, key must be s[hort], m[edium] or l[ong].
    -f filename    Use specified file as input.
    -h             Help dialog.

Gradle task looks like:

task run (type: JavaExec){
    description = "Secure algorythm testing"
    main = 'main.Test'
    classpath = sourceSets.main.runtimeClasspath
}

I've tried running gradle run -h and it does not work.

xlm
  • 6,854
  • 14
  • 53
  • 55
RecuencoJones
  • 2,747
  • 3
  • 22
  • 21

7 Answers7

126

Gradle 4.9+

gradle run --args='arg1 arg2'

This assumes your build.gradle is configured with the Application plugin. Your build.gradle should look similar to this:

plugins {
  // Implicitly applies Java plugin
  id: 'application'
}

application {
  // URI of your main class/application's entry point (required)
  mainClassName = 'org.gradle.sample.Main'
}

Pre-Gradle 4.9

Include the following in your build.gradle:

run {
    if (project.hasProperty("appArgs")) {
        args Eval.me(appArgs)
    }
}

Then to run: gradle run -PappArgs="['arg1', 'args2']"

xlm
  • 6,854
  • 14
  • 53
  • 55
108

Since Gradle 4.9, the command line arguments can be passed with --args. For example, if you want to launch the application with command line arguments foo --bar, you can use

gradle run --args='foo --bar'

See Also Gradle Application Plugin

How to upgrade Gradle wrapper

AMing
  • 5,532
  • 2
  • 24
  • 15
  • 1
    Is the ' expected or a typo? Should all arguments be passed as a string delimited by single quotes? – RecuencoJones Jul 20 '18 at 08:32
  • @RecuencoJones Fixed per https://docs.gradle.org/current/userguide/application_plugin.html#sec:application_usage – Drew Stephens Aug 02 '18 at 13:23
  • 1
    gradle run --args='foo --bar' – Jim Flood Aug 05 '18 at 16:38
  • 4
    `'foo --bar'` is confusing, why not just use `'foo bar'`. – Eric Sep 07 '18 at 07:37
  • 4
    @EricWang These are arbitrary command line arguments a program may need. It's nice to show that gradle supports any kind of arguments, since the raw string is passed to the built application. – Joffrey Nov 28 '18 at 10:39
  • If you have `args` defined in your `run` block, per Claudio's answer below, then they will *all* be overridden by your `--args` flag. In other words, gradle doesn't try to merge the two. –  Aug 02 '19 at 14:02
  • If you face issues with gradle run --args='foo --bar', use " " quotation marks instead of ' '. For instance : gradle run --args="arg1 arg2". – keita063 Mar 29 '21 at 12:03
38

If you want to use the same set of arguments all the time, the following is all you need.

run {
    args = ["--myarg1", "--myarg2"]
}
Claudio Fahey
  • 730
  • 6
  • 7
  • 3
    Ok, for absolute beginners like me : in order to be able to define run task your build.gradle should contain following two lines: apply plugin:'application' mainClassName="" Otherwise, you cannot define the run method in the buuild.gradle – Sandeep Aug 09 '18 at 07:07
  • 1
    I'm using the `id 'application'` plugin and this was the answer I needed (it works). – Big Rich Oct 30 '19 at 16:42
  • 1
    I am getting "unresolved reference: args". Gradle 7.3. – Henning Nov 28 '21 at 16:12
29

Sorry for answering so late.

I figured an answer alike to @xlm 's:

task run (type: JavaExec, dependsOn: classes){
    if(project.hasProperty('myargs')){
        args(myargs.split(','))
    }
    description = "Secure algorythm testing"
    main = "main.Test"
    classpath = sourceSets.main.runtimeClasspath
}

And invoke like:

gradle run -Pmyargs=-d,s
RecuencoJones
  • 2,747
  • 3
  • 22
  • 21
6

You can find the solution in Problems passing system properties and parameters when running Java class via Gradle . Both involve the use of the args property

Also you should read the difference between passing with -D or with -P that is explained in the Gradle documentation

Community
  • 1
  • 1
  • Saw this too. Still looking. All of these methods seem to want to edit/massage the current properties and pass them along. Command line and Java properties for running an application or service are akin to "Context" or "Configuration" setting. It would be better to have a plug-in that does things like "run parameters" as a side-by-side profiles or something. – will Dec 08 '16 at 04:41
6

Of course the answers above all do the job, but still i would like to use something like

gradle run path1 path2

well this can't be done, but what if we can:

gralde run --- path1 path2

If you think it is more elegant, then you can do it, the trick is to process the command line and modify it before gradle does, this can be done by using init scripts

The init script below:

  1. Process the command line and remove --- and all other arguments following '---'
  2. Add property 'appArgs' to gradle.ext

So in your run task (or JavaExec, Exec) you can:

if (project.gradle.hasProperty("appArgs")) {
                List<String> appArgs = project.gradle.appArgs;

                args appArgs

 }

The init script is:

import org.gradle.api.invocation.Gradle

Gradle aGradle = gradle

StartParameter startParameter = aGradle.startParameter

List tasks = startParameter.getTaskRequests();

List<String> appArgs = new ArrayList<>()

tasks.forEach {
   List<String> args = it.getArgs();


   Iterator<String> argsI = args.iterator();

   while (argsI.hasNext()) {

      String arg = argsI.next();

      // remove '---' and all that follow
      if (arg == "---") {
         argsI.remove();

         while (argsI.hasNext()) {

            arg = argsI.next();

            // and add it to appArgs
            appArgs.add(arg);

            argsI.remove();

        }
    }
}

}


   aGradle.ext.appArgs = appArgs

Limitations:

  1. I was forced to use '---' and not '--'
  2. You have to add some global init script

If you don't like global init script, you can specify it in command line

gradle -I init.gradle run --- f:/temp/x.xml

Or better add an alias to your shell:

gradleapp run --- f:/temp/x.xml
Boaz Nahum
  • 1,049
  • 8
  • 9
  • 2
    This works great ... if none of my arguments start with a dash. This makes it useless for common [command line parsers](https://commons.apache.org/proper/commons-cli/usage.html) :(. As soon as that happens, gradle seems to treat that arg as an argument to gradle (I don't think the `argsI.remove()` is having the desired effect). Suggestions? – Krease Jan 22 '18 at 18:42
4

You need to pass them as args to the task using project properties, something like:

args = [project.property('h')]

added to your task definition (see the dsl docs)

Then you can run it as:

gradle -Ph run
cjstehno
  • 13,468
  • 4
  • 44
  • 56