JBIDE-28730: Wrong editor opens while debugging quarkus project

[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?

[olkornii]

@jeffmaury Still same error, see video:

[jeffmaury]

@jeffmaury Still same error, see video:

This is a non bug. The projects are created with the same Maven coordinates as you did not go to the second screen of the wizard and the remote Java debug configuration is created by M2E that looks at the Maven console and automatically launches the Java debug when it sees a message like: Listening for transport dt_socket at address: 60172 So in order to associate a project with the new debug configuration, it retrieves the maven coordinates and try to find a project from the workspace. As both projects have the same Maven coordinates, then the first found is chosen. So I'm going to close this PR as main branch is correct.