[jboss-jira] [JBoss JIRA] (WFCORE-4246) FileSystemDeploymentService#handleNotification() can create an unneeded deployment marker file even if scanEnabled="false" is specified
Masafumi Miura (Jira)
issues at jboss.org
Tue Dec 4 22:36:00 EST 2018
[ https://issues.jboss.org/browse/WFCORE-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Masafumi Miura moved JBEAP-16000 to WFCORE-4246:
------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-4246 (was: JBEAP-16000)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Deployment Scanner
(was: Deployment Scanner)
Affects Version/s: 7.0.0.Final
(was: 7.1.5.GA)
> 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.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
More information about the jboss-jira
mailing list