You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem with this approach is that you need to keep in mind the proper ordering of args (e.g. -D args before -jar arg. or -javaagent arg order etc.)
Proposal is to enhance JavaExecFork to support running java application declaratively e.g.
jarFile = "$buildDir/libs/some-fat-jar.jar"
javaagent = "$buildDir/agent/some-agent.jar" //optional or can be moved to jvmArgs
jvmArgs = [ '-Dconfig.file=src/main/resources/some.conf' ]
waitForPort = 30000
stopAfter = xyz
...
The text was updated successfully, but these errors were encountered:
lukasito
changed the title
Support for declaring java -jar processes declaratively
Declarative support for java -jar processes
Feb 27, 2019
My build.gradle script couldn't resolve executable = Jvm.current().getJavaExecutable().getAbsolutePath(), so I added a full path like executable = org.gradle.internal.jvm.Jvm.current().getJavaExecutable().getAbsolutePath() and it works!
Currently workaround for this is to use
ExecFork
task and use it as follows:Problem with this approach is that you need to keep in mind the proper ordering of args (e.g. -D args before -jar arg. or -javaagent arg order etc.)
Proposal is to enhance
JavaExecFork
to support running java application declaratively e.g.The text was updated successfully, but these errors were encountered: