[jbosstools-issues] [JBoss JIRA] (JBIDE-22057) Changes done to OpenShift application are thrown away when debugging is enabled

[Marián Labuda (JIRA)]

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

Marián Labuda updated JBIDE-22057:
----------------------------------
    Description: 
When I have an OpenShift application and I do some changes locally which are published via rsync and application is not rebuilt (e.g. editing index.xhtml), enabling of debugging discard those changes and start debugging on something different.

I think this is caused because enabling debugging inject another env. vars to OpenShift and it spin up a new pod, were changes from rsync are not present.

  was:
When I have an OpenShift application and I do some changes locally which are published via rsync, enabling of debugging discard those changes and start debugging on something different.

I think this is caused because enabling debugging inject another env. vars to OpenShift and it spin up a new pod, were changes from rsync are not present.



> Changes done to OpenShift application are thrown away when debugging is enabled
> -------------------------------------------------------------------------------
>
>                 Key: JBIDE-22057
>                 URL: https://issues.jboss.org/browse/JBIDE-22057
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.3.1.CR1
>            Reporter: Marián Labuda
>            Priority: Critical
>              Labels: openshift_v3, server_adapter
>
> When I have an OpenShift application and I do some changes locally which are published via rsync and application is not rebuilt (e.g. editing index.xhtml), enabling of debugging discard those changes and start debugging on something different.
> I think this is caused because enabling debugging inject another env. vars to OpenShift and it spin up a new pod, were changes from rsync are not present.



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