[jira] [Updated] (SUREFIRE-1801) New TCP communication mode defers "Listening for transport" debug message

["Tibor Digana (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SUREFIRE-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tibor Digana updated SUREFIRE-1801:
-----------------------------------
    Fix Version/s: 3.0.0-M6

> New TCP communication mode defers "Listening for transport" debug message
> -------------------------------------------------------------------------
>
>                 Key: SUREFIRE-1801
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1801
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: process forking
>    Affects Versions: 3.0.0-M5
>         Environment: $ mvn -version
> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
> Maven home: C:\Develop\some-project\middleware\_develop\maven\default
> Java version: 11.0.7, vendor: AdoptOpenJDK, runtime: C:\Develop\some-project\middleware\_develop\java\default
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>            Reporter: Falko Modler
>            Priority: Minor
>             Fix For: 3.0.0-M6
>
>
> When using
> {code:xml}
> <forkNode implementation="org.apache.maven.plugin.surefire.extensions.SurefireForkNodeFactory"/>
> {code}
> and {{-Dmaven.surefire.debug}} you see the message
> {noformat}
> Listening for transport dt_socket at address: 5005
> {noformat}
> _only after_ you have connected the debugger, which defeats the whole point of this message and leaves the user under the impression that test execution is stuck before opening the debug port.
> In "legacy" mode the message is displayed as expected (before connecting the debugger).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)