-
Bug
-
Resolution: Done
-
Trivial
-
7.1.0.Final
-
None
-
-
Workaround Exists
-
-
Low
If the scan-intervall is set to <1 the scanner should only scan deployments during startup (documented within schema).
If the value is set expicit to "0" no re-deploy happen if anything is changed after startup.
If the attribute scan-interval is removed it should be the same behaviour because the schema default is "0".
But the scan is still enabled.