deployment-scanner*
Allows configuration of an additional location where deployment
content can be stored.
| Name | Type | Default | Description |
|---|---|---|---|
| name | string | default | |
| path | FIXME | The actual filesystem path. Treated as an absolute path, unless the 'relative-to' attribute is specified, in which case the value is treated as relative to that path. | |
| relative-to | string | Reference to a filesystem path defined in the "paths" section of the server configuration. | |
| scan-enabled | boolean | true | Flag indicating that all scanning (including initial scanning at startup) should be enabled or disabled. |
| scan-interval | int | 0 | Periodic interval, in milliseconds, at which the repository should be scanned for changes. A value of less than 1 indicates the repository should only be scanned at initial startup. |
| auto-deploy-zipped | boolean | true | Controls whether zipped deployment content should be automatically deployed by the scanner without requiring the user to add a .dodeploy marker file. |
| auto-deploy-exploded | boolean | false | Controls whether exploded deployment content should be automatically deployed by the scanner without requiring the user to add a .dodeploy marker file. Setting this to 'true' is not recommended for anything but basic development scenarios, as there is no way to ensure that deployment will not occur in the middle of changes to the content. |
| auto-deploy-xml | boolean | true | Controls whether xml deployment content should be automatically deployed by the scanner without requiring the user to add a .dodeploy marker file. |
| deployment-timeout | int | 600 | Timeout used, in seconds, for deployment operations. If an individual deployment operation takes longer than this timeout it will be canceled and marked as failed. |
| runtime-failure-causes-rollback | boolean | false | Controls whether a runtime failure of a deployment causes a rollback of the deployment as well as all other (maybe unrelated) deployments as part of the scan operation. |