You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@knox.apache.org by "Kevin Minder (JIRA)" <ji...@apache.org> on 2014/03/06 18:54:47 UTC

[jira] [Resolved] (KNOX-140) Support a forced redeploy of topologies

     [ https://issues.apache.org/jira/browse/KNOX-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Minder resolved KNOX-140.
-------------------------------

    Resolution: Duplicate

> Support a forced redeploy of topologies
> ---------------------------------------
>
>                 Key: KNOX-140
>                 URL: https://issues.apache.org/jira/browse/KNOX-140
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: Server
>    Affects Versions: 0.3.0
>            Reporter: Kevin Minder
>             Fix For: 0.4.0
>
>
> There will likely be cases where a forced redeploy of all topologies is required.  The main use case is when Knox is upgraded or possibly when gateway-site.xml is changed.  One way to do this might be to add a --redeploy switch to gateway.jar.  Thought needs to be given as to how this should interact with --nostart.  Should --redeploy imply --nostart?



--
This message was sent by Atlassian JIRA
(v6.2#6252)