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

Konrad Windszus closed SUREFIRE-2182.
-------------------------------------
    Fix Version/s: 3.x-candidate
       Resolution: Fixed

Fixed in 
https://github.com/apache/maven-surefire/commit/49e6607fb3b5a0690cddb4fe371b98f80859c843

> Log starter implementation on DEBUG level
> -----------------------------------------
>
>                 Key: SUREFIRE-2182
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-2182
>             Project: Maven Surefire
>          Issue Type: Improvement
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: 3.x-candidate
>
>
> In order to ease debugging classpath issues the fork configuration determined 
> by 
> [AbstractSurefireMojo.createForkConfiguration(...)|https://github.com/apache/maven-surefire/blob/0998f10bb486f79f40d2d4262798b1f53a5ff286/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java#L2216]
>  should be logged with debug level for when using the fork starter. Similarly 
> a DEBUG log entry should be emitted when the in-process starter is being used.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to