Details
-
Bug
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
3.0.0-M5
-
None
-
$ 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"$ 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"
Description
When using
<forkNode implementation="org.apache.maven.plugin.surefire.extensions.SurefireForkNodeFactory"/>
and -Dmaven.surefire.debug you see the message
Listening for transport dt_socket at address: 5005
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).
Attachments
Issue Links
- is related to
-
SUREFIRE-1881 Java agent printing to native console makes build block when using SurefireForkNodeFactory
-
- Closed
-