Settings ProjectGroovyClassPathSettings/en: Unterschied zwischen den Versionen
Zur Navigation springen
Zur Suche springen
Cg (Diskussion | Beiträge) |
Cg (Diskussion | Beiträge) |
||
| Zeile 1: | Zeile 1: | ||
== Groovy Action Blocks and ClassPath == |
== Groovy Action Blocks and ClassPath == |
||
Groovy actions are executed in a separate Java Virtual Machine ( |
Groovy actions are executed in a separate Java Virtual Machine (JVM). This JVM can be either 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), |
||
whereas implicitly (i.e. automatically) started JVMs get their class path from the user settings. |
whereas implicitly (i.e. automatically) started JVMs get their class path from the user settings. |
||
Version vom 26. Juli 2018, 07:53 Uhr
Groovy Action Blocks and ClassPath[Bearbeiten]
Groovy actions are executed in a separate Java Virtual Machine (JVM). This JVM can be either 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.
The "Settings" - "Project Management" - "Groovy Class Path" dialog is used to configure this class path.
