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 
> cannot debug dynamically changing code.
>
> (My Kiss <https://kissweb.org> system uses a microservice architecture 
> that recompiles files at runtime if they change.  NetBeans cannot 
> debug classes that have changed, meaning you can't develop while the 
> system is running - a chief benefit of the system.)
>
> I wanted to see if, years later, the problem was fixed, but I ran into 
> other problems (multiple source roots).
>
> At the time (years ago), I was looking for commercial support to fix 
> that problem.  Being unable to find a reasonable solution, I just 
> dropped the whole matter. I realized two things:
>
> 1. The IntelliJ Java debugger works correctly.  (It is the only one.)
>
> 2. IntelliJ has an open-source version that has all of the correct 
> code for its debugger to handle dynamically changing code.
>
> So, if there is interest in fixing the problem, the code is in the 
> open-source release of IntelliJ.
>
> Thanks.
>
> Blake
>
>