]
Brian Stansberry moved WFLY-2503 to WFCORE-331:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-331 (was: WFLY-2503)
Component/s: Domain Management
(was: Domain Management)
Configurable location for deployment scanner marker files
---------------------------------------------------------
Key: WFCORE-331
URL:
https://issues.jboss.org/browse/WFCORE-331
Project: WildFly Core
Issue Type: Feature Request
Components: Domain Management
Reporter: Brian Stansberry
Add marker-dir and marker-dir-relative-to attributes to the deployment scanner resource.
These control where the marker files are written, with the default being the dir being
scanned itself.
The idea here is to allow sharing of a deployments/ dir by letting users redirect the
markers to some other location.
To store in a server-specific subdir of deployments (making the markers still fairly
accessible the user):
{code}
<deployment-scanner path="deployments"
relative-to="jboss.server.base.dir" scan-interval="5000"
marker-dir="deployments/${jboss.node.name}"
marker-dir-relative-to="jboss.server.base.dir"
/>
{code}
To store the markers in the data dir, out of sight, out of mind:
{code}
<deployment-scanner path="deployments"
relative-to="jboss.server.base.dir" scan-interval="5000"
marker-dir="deployment-scanner-markers"
marker-dir-relative-to="jboss.server.data.dir"
/>
{code}
This all sounds simple enough, but anyone looking into it *must* assume this will be a
highly complex task, as the scanner itself is very complex and assumes that the
deployments and the markers are in the same dir. Extremely extensive test coverage will be
required.