SVT: App does not restart after doing Hot code replacement while Debugger is started.

I have installed Liberty Tools Eclipse 25.0.6 - as part of this TER - https://github.ibm.com/websphere/system-test/issues/1498

I started the Debugger, and while it is still running, I tried to change the method signature.

I tried to change the method signature - from private void issueEndLinesHtmlTest(PrintWriter out) to private void issueEndLinesHtmlTest(PrintWriter out, String test)
and saved the file.

However, the App didn't restart, and I did not see any pop-up for the Hot Code Replacement.

The only message I see in the console is that the app source compilation was successful:

[[1;34mINFO[m] [AUDIT  ] CWWKZ0001I: Application AcmeWebEjbEar started in 269.746 seconds.
[[1;34mINFO[m] AcmeAnnuityWeb source compilation was successful.
[[1;34mINFO[m] AcmeAnnuityWeb source compilation was successful.

Steps to recreate:

1. Get the Acme App from this repo (acme-ee10 branch) - https://github.ibm.com/was-svt/acme-ee/tree/acme-ee10
2. Update the acme-ee/pom.xml with this for Liberty Maven Plugin.

<!-- Enable liberty-maven plugin -->     
      			<plugin>
        			<groupId>io.openliberty.tools</groupId>
        			<artifactId>liberty-maven-plugin</artifactId>
       
       				<version>3.11.4</version>
      				<configuration>
      					<stripVersion>true</stripVersion>
       					<keepTempContainerfile>false</keepTempContainerfile>
      				</configuration>
      			
      			</plugin>   

3. Start the App in Debug mode using the Liberty Tools.
4. Make a change in the method com.ibm.wssvt.acme.annuity.web.AnnuityWebServlet,
   from private void issueEndLinesHtmlTest(PrintWriter out) to private void issueEndLinesHtmlTest(PrintWriter out, String test)
5. The App does not restart as expected.

Reproduce the issue in Liberty Tools Eclipse with the Liberty Maven Plugin 3.11.4, using the AcmeAnnuityWeb change in com.ibm.wssvt.acme.annuity.web.AnnuityWebServlet while the debugger is running. Trace the debugger and hot-code-replacement handling from that scenario; it is done when the application restarts and the expected Hot Code Replacement prompt appears after the method signature change.