On Mon, Oct 10, 2022 at 9:55 AM Eric Bresie <[email protected]> wrote:
> Just out of curiosity, was a previous debug session still active while > changes in code where made? > No. > > Did it get rebuilt after changes where made? > My Groovy modules are compiled and loaded at runtime. When I change a Groovy source file, the system notices the file time change. The next time it is called, it is dynamically re-loaded. Once re-loaded, NetBeans still uses its old pointers. It doesn't refresh its pointers when the module is re-loaded. (Source code for this is at https://github.com/blakemcbride/Kiss Also, it has been used in production for several years without any problems.) > I sometimes find if it is still running, it may not update what is > available until it has been rebuilt and/or restarted > Yea, that's the problem. If I stop and restart the system, all is well. The problem is my system has over 9,000 Java classes. Bringing the system down and back up is too costly. Additionally, because o the way I dynamically load code, I can update a production server without bringing it down. So it significantly decreases development time and allows non-disruptive production updates. Thanks. Blake McBride
