IDEA 2026.1 - Debugger API changes that breaks the plugin

[davsclaus]

https://blog.jetbrains.com/platform/2026/01/platform-debugger-architecture-redesign-for-remote-development-in-2026-1/

[rastislavpapp]

I think I got this. I'll submit the PR soon. But I've detected a curious behavior, that I think wasn't there before. I'm trying to set-up debugging in a junit test, and the order of camel context initialization in TransientCamelContextManager is:

• setupRoutes
• tryStartCamelContext

During the setupRoutes phase, source locations are added to the LineNumberAware classes, but only if needed. (If debugging / tracing / source location is enabled). But debugging is detected in AbstractCamelContext#doInit, which is part of the latter operation (tryStartCamelContext). So debugging (at least in junit tests) is not working, because of the missing source locations.

So I had to enable the debugging in the test manually, which was also a bit of unintuitive - CamelTestSupport#isUseDebugger is deprecated (and no longer invoked, so does nothing), and says to Use the accessors from testConfiguration() method. Which does not provide accessors for enabling the debugging :-)
Only way to enable it I found was overriding CamelTestSupport#configureContext, and adding an empty breakpoint, like this:

public class SomeTest extends CamelTestSupport {

    @Override
    public void configureContext(CamelContextConfiguration camelContextConfiguration) {
        super.configureContext(camelContextConfiguration);
        camelContextConfiguration.withBreakpoint(new DebugBreakpoint() {
            @Override
            protected void debugBefore(Exchange exchange, Processor processor, ProcessorDefinition<?> definition, String id, String label) {

            }

            @Override
            protected void debugAfter(Exchange exchange, Processor processor, ProcessorDefinition<?> definition, String id, String label, long timeTaken) {

            }
        });
    }

which I did not find very user friendly.