Settings ExternalScriptInterpreters GroovyClassPathSettings/en: Unterschied zwischen den Versionen
Zur Navigation springen
Zur Suche springen
Cg (Diskussion | Beiträge) (Die Seite wurde neu angelegt: „== Groovy Class Path Settings == ===== Groovy Action Blocks and ClassPath ===== Groovy actions are executed in a separate Java Virtual Machine (JVM). This JV…“) |
Cg (Diskussion | Beiträge) |
||
| Zeile 3: | Zeile 3: | ||
===== Groovy Action Blocks and ClassPath ===== |
===== Groovy Action Blocks and ClassPath ===== |
||
Groovy actions are executed in a separate Java Virtual Machine (JVM). This JVM can be |
Groovy actions are executed in a separate Java Virtual Machine (JVM). This JVM can be started explicitly via "[<code>Start Java on Local Machine</code>]" action blocks, via a shell script, or implicitly whenever the very first groovy action is executed. |
||
Explicitly (i.e. manually) started JVMs can be configured via the "[<code>Add JAR</code>]" action to include any required class libraries (".jar" files), |
Explicitly (i.e. manually) started JVMs can be configured via the "[<code>Add JAR</code>]" action to include any required class libraries (".jar" files), |
||
Aktuelle Version vom 29. April 2025, 09:18 Uhr
Groovy Class Path Settings[Bearbeiten]
Groovy Action Blocks and ClassPath[Bearbeiten]
Groovy actions are executed in a separate Java Virtual Machine (JVM). This JVM can be started explicitly via "[Start Java on Local Machine]" action blocks, via a shell script, or implicitly whenever the very first groovy action is executed.
Explicitly (i.e. manually) started JVMs can be configured via the "[Add JAR]" action to include any required class libraries (".jar" files),
whereas implicitly (i.e. automatically) started JVMs get their class path from the user settings.
Jar or Folder[Bearbeiten]
Defines additional Jar files and pathes which are passed to groovy for class resolving.
Back to "External Script Interpreter Settings"
Back to the main page "Settings"
