This message was deleted.
# community-supports
Slackbot
11/26/2022, 4:41 PMThis message was deleted.
e
Eric Kolotyluk
11/26/2022, 4:42 PMHowever, I am able to run my code from the IntelliJ UI... but now I want to be able to run it from the gradle command line...
c
Chris Lee
11/26/2022, 4:43 PMit needs toe add-modules there, which is two arguments:
Copy code
applicationDefaultJvmArgs += "--enable-preview"
applicationDefaultJvmArgs += "--add-modules"
applicationDefaultJvmArgs += "jdk.incubator.concurrent"Chris Lee
11/26/2022, 4:45 PMAlternate syntax (find this clearer):
Copy code
applicationDefaultJvmArgs.addAll(listOf("--enable-preview", "--add-modules", "jdk.incubator.concurrent"))e
Eric Kolotyluk
11/26/2022, 4:45 PM Copy code
eric.kolotyluk@Y2RCV7009N loom-laboratory % ./gradlew run
> Task :run
WARNING: Using incubator modules: jdk.incubator.concurrent
Hello world!
hello loom
BUILD SUCCESSFUL in 525ms
2 actionable tasks: 1 executed, 1 up-to-datec
Chris Lee
11/26/2022, 4:45 PMcool.
e
Eric Kolotyluk
11/26/2022, 4:46 PMSome things in Gradle are strings... and some are lists of strings...
c
Chris Lee
11/26/2022, 4:48 PMthis one is a list of arguments. Args are often confusing as command-line shells do some parsing, so folks assume they can drop the command line string directly into a process executor (whether it’s Gradle or not - any language, mechanism has this challenge), without first breaking them apart. Also applies to wildcards that the shell will expand.
e
Eric Kolotyluk
11/26/2022, 4:48 PMYup
Eric Kolotyluk
11/26/2022, 4:49 PMFor the curious
8 Views