[jboss-jira] [JBoss JIRA] (WFCORE-27) Deployment scanner treats zipped content as unmanaged

[Brian Stansberry (JIRA)]

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

Brian Stansberry moved WFLY-3320 to WFCORE-27:
----------------------------------------------

              Project: WildFly Core  (was: WildFly)
                  Key: WFCORE-27  (was: WFLY-3320)
    Affects Version/s:     (was: 8.0.0.Final)
                           (was: 8.1.0.CR1)
          Component/s: Domain Management
                           (was: Domain Management)
        Fix Version/s: 1.0.0.Alpha4
                           (was: 9.0.0.CR1)


> Deployment scanner treats zipped content as unmanaged
> -----------------------------------------------------
>
>                 Key: WFCORE-27
>                 URL: https://issues.jboss.org/browse/WFCORE-27
>             Project: WildFly Core
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Domain Management
>            Reporter: Brian Stansberry
>            Assignee: Emmanuel Hugonnet
>             Fix For: 1.0.0.Alpha4
>
>
> A really old commit[1] had the effect that both exploded and zipped deployments in the deployments/ dir are treated as unmanaged content. The original intent was zipped content should be uploaded to the content repo.
> This may be ok as I haven't heard about issues it causes. Emmanuel Hugonnet noted that there's an issue with JSP compilation work files from an deployment with a later timestamp not getting discarded if the scanner file has an older timestamp, but that is more an issue with how the JSP compilation work files are maintained than a problem with the scanner creating unmanaged deployments. Switching to managed deployments would fix that, but only for archives.
> [1] https://github.com/wildfly/wildfly/commit/fd2d9bc1



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)