[
https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-21857:
-------------------------------------
[~tmader] Where are you looking to discover this low level information in the debugger?
Can you think of any workaround? Is this an error in eap/wf keeping the old class around?
Or is Eclipse debugger caching it somehow? Is there any api we can use to force the
debugger to forget some classes or packages? Thats probably not a safe workaround, though,
since the same package could be used in multiple deployments.
Also I know I haven't experienced this before, but then I don't think I tested it
super-methodically because it seemed to work. Is it a guarantee the old class's
presence prevents any further changes? Or is it kinda based on which class happens to be
at the top of the list / set / etc?
Hot class reload doesn't work on OpenShift
------------------------------------------
Key: JBIDE-21857
URL:
https://issues.jboss.org/browse/JBIDE-21857
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.Beta2
Reporter: Fred Bricon
Assignee: Thomas Mäder
Priority: Blocker
Fix For: 4.3.1.CR1
When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class
file will :
- work sometimes when only the content of the method changed, but could fail in some
other occasions with the Debugger saying the JDK is out of sync
- will always fail if a method signature changed, the debugger saying JDK is out of sync
Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as
opposed to the same tweak ahen running on a local EAP server)
This may be caused by running OpenJDK? Does it support the same level of debugging as
Oracle JDK?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)