-
Notifications
You must be signed in to change notification settings - Fork 6
Configuration
Antonio Robirosa edited this page May 15, 2021
·
9 revisions
All the configuration settings with their default value are stored in project.properties in the extension.
If you want to change any setting, just override it in local.properties.
| Setting | Default | Possible Values | Description |
|---|---|---|---|
| deploymentscripts.resources.folder | /resources | String | Root folder of the scripts |
| deploymentscripts.update.folder | update-deployment-scripts | String | Name of the folder containing the UPDATE deployment scripts |
| deploymentscripts.init.folder | init-deployment-scripts | String | Name of the folder containing the INIT deployment scripts |
| deploymentscripts.init. junittenant.createessentialdata | true | true or false | Do we start the import of the essential and project data and run the deployment scripts during the initialization of the junit tenant? |
| deploymentscripts.environment.current | No default | DEV, TEST, INT and PRODUCTION | Name of the environment to which the machine belongs |
| deploymentscripts.impex.locale | en_US | Code of a java locale | Locale used to import the impex files |
| deploymentscripts.createdata.type | ESSENTIAL | ESSENTIAL or PROJECT | When are the deployment scripts run: during the create essential data or create project data step? Please remember that the create project data step is optional, while create essential data is always run |
| deploymentscripts.stacktrace.maximumlength | 0 | Any integer | If there is error running a script, save up to this number of bytes of the stacktrace in the database. 0 means no limit and can be safely used with Oracle, MySQL, Microsoft SQL and HyperSQL databases |