Re: Improving the Java debugger

Thanks for the info, Maciej!I didn't know NB had an "Apply Changes." Last time I investigated this problem with NB (back in 2022), I posted my problems to this group. Either NB didn't have that ability back then, or no one told me about it. I'm not completely sure how to even try it now because of

Re: Improving the Java debugger

Haven't tested your code, but in NB you can "Apply Code Changes". This works for reloading the body of any function in Java/JVM. It works when a project is opened in NB (specific module) and the project is run in debug mode in NB (e.g., deployed to Tomcat). Reloading method bodies even worked i

Re: Improving the Java debugger

I presume that this ability is somewhat new since NetBeans of 2022 could not handle changing classes. I spent a bunch of time with it, as well as on this group on that matter, in 2022. (I can't test it now because I am having trouble indicating multiple source roots to NetBeans.) Thanks. Blake

Re: Improving the Java debugger

NetBeans works well in those use cases, just needs to be aware of the project structure, so when a change is detected in the class it can reload that for the debugger. On 9/19/25 07:57, Blake McBride wrote: Greetings, Some time ago, I reported the fact that the Java debugger in NetBeans cann

Improving the Java debugger

Greetings, Some time ago, I reported the fact that the Java debugger in NetBeans cannot debug dynamically changing code. (My Kiss system uses a microservice architecture that recompiles files at runtime if they change. NetBeans cannot debug classes that have changed, meanin