[
https://issues.jboss.org/browse/JBIDE-22057?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-22057 at 4/5/16 11:19 AM:
-------------------------------------------------------------------
[~scabanovich] out of my guts I'd think that this is cause (as far as I can remember
we debuggin to enabled in the env vars and also specify the debug port in the dc).
If this turns out to be true then this would mean that we'd have to do an initial
rsync when restarting in debug mode I think
was (Author: adietish):
[~scabanovich] out of my guts I'd think that this is cause (as far as I can remember
we debuggin to enabled in the env vars and also specify the debug port in the dc).
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
Fix For: 4.4.0.Alpha1
When I have an OpenShift application and I do any changes locally which are either
incrementally or fully published, 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 but does not keep changes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)