Fixes #13472 - Support multiple directories to be scanned by deployment-scanner.

[sbordet]

• Updated jetty-deployment-scanner.xml to support a CSV list of directories.
• Updated documentation.
• Added tests, and cleaned up XmlConfigurationTest.

[pzygielo]

Tested with locally built (69c94c9).
Works very, very fine with multiple webdirs separated with ,.

Thanks!

[sbordet]

@pzygielo thanks for the feedback!

[gregw]

@sbordet If we support multiple directories, do we handle a foo.war in one directory and a foo.xml in another and a foo.properties in yet another? Should we?

Should we support property files in a deployment directory that apply to all webapps from that directory?

[sbordet]

@gregw I think technically it would be possible to have foo.war in one directory, and foo.properties in another directory, but that would be extremely unlikely -- I don't see a user wanting to do that.

Should we support property files in a deployment directory that apply to all webapps from that directory?

I don't think so. If you mean a single *.properties file that specifies the environment for a directory that only deploys one environment, then I think it's assuming too much.

Multiple directories may be used for different environments, but I can also see multiple directories used for multiple web application sources (e.g. deptA-webapps, deptB-webapps), that each can deploy web applications for different environments.

I would just leave it to the users to not make it too complicated; we just offer multiple directories.

[janbartel]

Is this true? Must they be relative to $JETTY_BASE? The javadoc on XmlConfiguration.csvSplitAndResolvePaths says it accepts relative or absolute paths.

[sbordet]

I clarified the module comment, in this file as well as in other files.