[
https://issues.jboss.org/browse/JBIDE-22057?page=com.atlassian.jira.plugi...
]
Marián Labuda commented on JBIDE-22057:
---------------------------------------
[~scabanovich]
1) Nope. Changes are still not there. Conclusion: Restarting in debug mode does not fix
it.
2) Changes are there. Conclusion: mode does matter.
I still think the cause is, as I wrote in description - when we restart a server adapter
in debug mode, we change deployment config and therefore a new pod is spinned up where
changes are not propagated (new pod mean new instance of EAP). But I could be wrong...
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)