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

Wed Apr 4 03:27:47 EDT 2012

    [ https://issues.jboss.org/browse/AS7-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681516#comment-12681516 ] 

Dimitris Andreadis commented on AS7-4383:
-----------------------------------------

I think those changes just screw up completely the way the new scanner is supposed to work. Either you have marker files, or you don't.

IMO, we should have 2 deployment scanner types, new style and old style, and be able to configure them independently.

> 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: 7.2.0.Alpha1
>
>
> 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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira