[jboss-jira] [JBoss JIRA] (AS7-4383) Mode to disable writing deployment outcome files to deployment scanner dir

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/AS7-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry resolved AS7-4383.
-----------------------------------

    Fix Version/s: No Release
                       (was: 7.2.0.Alpha1)
       Resolution: Won't Fix


If a user uses the CLI or admin console to undeploy a deployment added by the scanner, we put down an .undeployed marker to record that, so the scanner doesn't just come along and deploy it again. So this JIRA would break that functionality, plus probably others.
                
> Mode to disable writing deployment outcome files to deployment scanner dir
> --------------------------------------------------------------------------
>
>                 Key: AS7-4383
>                 URL: https://issues.jboss.org/browse/AS7-4383
>             Project: Application Server 7
>          Issue Type: Feature Request
>          Components: Domain Management
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: No Release
>
>
> Investigate adding a config option that disables writing the .isdeploying, .deployed, .isundeploying, .undeployed files to the deployment scanner dir.
> Idea is to make it possible to have multiple scanners on different nodes sharing the deployment directory, without having the markers from one interfere with another.
> This may not be practical at all in reality; needs investigation.
> Marker files created by the user to control deployment should still be supported.
> The .failed and .pending files are a bit of a gray area that need investigation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira