The devonfw-ide
defines a set of standard variables to your environment for configuration via variables[.bat]
files.
These environment variables are described by the following table.
Those variables printed bold are also exported in your shell (except for windows CMD that does not have such concept). Variables with the value -
are not set by default but may be set via configuration to override defaults.
Please note that we are trying to minimize any potential side-effect from devonfw-ide
to the outside world by reducing the number of variables and only exporting those that are required.
Variable | Value | Meaning |
---|---|---|
|
e.g. |
The top level directory of your |
|
|
You system path is adjusted by |
|
|
The platform independent home directory of the current user. In some edge-cases (e.g. in cygwin) this differs from |
|
|
List of tools that should be installed and upgraded by default for your current IDE. |
|
|
List of custom tools that should be installed additionally. See software for further details. |
|
|
List of IDEs that shall be used by developers in the project and therefore start-scripts are created on setup. |
|
|
A "backup" of |
|
|
The workspace you are currently in. Defaults to |
|
|
Absolute path to current workspace. Never touch this variable in any |
|
|
Path to JDK |
|
|
Path to your settings. To keep |
|
|
Path to your local maven repository. For projects without high security demands, you may change this to the maven default |
|
|
Path to Maven |
|
|
Maven options |
|
e.g. |
If set as |
|
|
Path to GraalVM |
|
|
Project specific or custom software-repository. |
|
|
Globally shared user-specific local software installation location. |
|
|
JVM options for Eclipse |
deprecated: |
|
Array with "feature groups" and "update site URLs" to customize required eclipse plugins. Deprecated - see Eclipse plugins. |
|
|
The edition of the tool |
|
|
The version of the tool |
|
|
An additional (newer) version of java that will be used to run java-based IDEs (e.g. eclipse or intellij). |
|
e.g. |
The arguments provided to the build-tool |
|
e.g. |
The arguments provided to the build-tool |
|
If value is not an empty string, the |
For each tool you can configure the version as «TOOL»_VERSION
. Example:
JAVA_VERSION=17.0.8.1_1
MVN_VERSION=3.9.4
However, instead of specifying an exact version number, you may also configure a version pattern:
JAVA_VERSION=17*
MVN_VERSION=3.9.*
This will always install the latest stable version matching the according version. As IDE-admin please take responsibility and choose wisely between stability and getting the latest fixes and security updates.