Users must choose between debugger HCR and application monitor HCR without assistance from tool

A small application may wish to use the default <applicationMonitor> config (polling for updates) in which case a "Hot Code Replace" (HCR)-like experience can be achieved even during a regular (non-Debug) "Start".

OTOH, for a larger app that takes longer (30, 60s, whatever) to restart, this is so slow that the only way to achieve an "HCR" experience will be to rely on the Eclipse Debugger HCR support. In this case the applicationMonitor updateTrigger will need to be set to disabled (or mbean).

So you really can't easily switch between Start or Debug and get HCR in both.

In WDT/LDT this issue was solved by having WDT use the mbean as a trigger....but it would avoid issuing the update notification if you were in Debug mode, letting the faster Debugger HCR do its thing.

This config would look like:
<applicationMonitor dropinsEnabled="false" updateTrigger="mbean" />
and IIUC, was generated as a configDropin by WDT.

NOTE

One caveat, note debugger HCR has limitations, e.g you can't add change/add method signatures.

Start by tracing how the applicationMonitor updateTrigger and debugger HCR interact during Start and Debug launches; the issue names the mbean trigger and a generated configDropin as the relevant behavior. Determine how to avoid application update notifications in Debug mode while retaining polling-like HCR during Start, and verify both workflows, including the debugger HCR limitations.