[jboss-jira] [JBoss JIRA] (WFCORE-1752) The deployment-overlay command fails to redeploy affected deployments

Brian Stansberry (JIRA) issues at jboss.org
Wed Aug 31 10:23:00 EDT 2016


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

Brian Stansberry commented on WFCORE-1752:
------------------------------------------

Is coupling to the runtime-name really the intended behavior? Or is that a bug? Or perhaps a design flaw?

I can see arguments both ways, so I'm curious what [~swd847] had in mind at the beginning.

Certainly the runtime-name needs to come into the picture in order to get the content into the running app; I'm asking here about the meaning of the "name" attribute in the deployment-overlay/deployment element.

> The deployment-overlay command fails to redeploy affected deployments
> ---------------------------------------------------------------------
>
>                 Key: WFCORE-1752
>                 URL: https://issues.jboss.org/browse/WFCORE-1752
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: CLI
>    Affects Versions: 3.0.0.Alpha5
>            Reporter: ehsavoie Hugonnet
>            Assignee: Alexey Loubyansky
>
> The deployment-overlay command fails to redeploy affected deployments if the runtime-name isn't the same as the deployment name. Since affected deployment to be redeployed should be running the couple runtime-name + enabled == true should be used to define which deployments are affected instead of using the deployment name since the name used in overlay is the runtime-name



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jboss-jira mailing list