JBIDE-28715: Quarkus run configurations starts the Java debugger

[jeffmaury]

Signed-off-by: Jeff MAURY jmaury@redhat.com

Pull Request Checklist

General

• Is this a blocking issue or new feature? If yes, QE needs to +1 this PR

Code

• Are method-/class-/variable-names meaningful?
• Are methods concise, not too long?
• Are catch blocks catching precise Exceptions only (no catch all)?

Testing

• Are there unit-tests?
• Are there integration tests (or at least a jira to tackle these)?
• Is the non-happy path working, too?
• Are other parts that use the same component still working fine?

Function

• Does it work?

[jeffmaury]

I don't see a real change here. starting application using Quarkus run config still starts debugger and hit breakspoints.

Can you share the output of the Maven console ?

[sbouchet]

I don't see a real change here. starting application using Quarkus run config still starts debugger and hit breakspoints.

Can you share the output of the Maven console ?

I was trying to do so , to show that even in run mode, i was seeing the debugger port listener message, but i can't anymore after several run then debug launches.

So i can't reproduce.