-
Notifications
You must be signed in to change notification settings - Fork 11
Settings: ViperServer
Linard Arquint edited this page Feb 17, 2022
·
2 revisions
This block contains all settings related to the ViperServer
- serverJars: A list of all the jar files required for the viperServer. The paths can point to a folder or a jar file. Allowed formats are: String, [String], BackendSpecific(String), BackendSpecific([String])
- customArguments: The command line arguments used for starting the Viper Server
-
backendSpecificCache: Use a separate cache for both backends, the option
$backendSpecificCache$
turns into"--backendSpecificCache"
or""
, depending on this setting - disableCaching: Disable the cache and completely reverify all files
- timeout: The time after which the startup of the ViperServer is considered failed.
-
viperServerPolicy: Specifies whether ViperServer should be started by the IDE or whether the IDE should attach to an existing instance of ViperServer. Possible values:
attach
,create
. Defaults tocreate
. - viperServerAddress: Specifies the address part of the URL that ViperServer is running on.
-
viperServerPort: Specifies the port part of the URL that ViperServer is running on. Only needed if viperServerPolicy is set to
attach
.
Default Settings:
"viperSettings.viperServerSettings": {
"v": "674a514867b1",
"serverJars": {
"windows": "$viperTools$/backends",
"linux": "$viperTools$/backends",
"mac": "$viperTools$/backends"
},
"customArguments": " $backendSpecificCache$",
"backendSpecificCache": true,
"disableCaching": false,
"timeout": 5000,
"viperServerPolicy": "create",
"viperServerAddress": "http://127.0.0.1",
"viperServerPort": 12345
}