FileSystemDeploymentService#handleNotification() can create an unneeded deployment marker file even if scanEnabled="false" is specified --------------------------------------------------------------------------------------------------------------------------------------- Key: WFCORE-4246 URL: https://issues.jboss.org/browse/WFCORE-4246 Project: WildFly Core Issue Type: Bug Components: Deployment Scanner Affects Versions: 7.0.0.Final Reporter: Masafumi Miura Assignee: ehsavoie Hugonnet Priority: Minor Even if scanEnabled="false" is specified in the deployment-scanner subsystem, a deployment marker can be created for files located under the deployment-scanner directory. This happens when deploying an application which has the same filename to the file through the management CLI. This behavior did not happen in EAP 6.4.x, but this happens since EAP 7.x because of FileSystemDeploymentService#handleNotification() processing. I think this behavior itself does not have a negative effect, so this is a minor issue. However, it's better to avoid creating an unneeded marker file.