[Commented] (SUREFIRE-1436) maven.surefire.debug in silent mode

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[Commented] (SUREFIRE-1436) maven.surefire.debug in silent mode

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SUREFIRE-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200883#comment-16200883 ]

Tibor Digana commented on SUREFIRE-1436:

What's expected?
Pls write direct issue summary.

> maven.surefire.debug in silent mode
> -----------------------------------
>                 Key: SUREFIRE-1436
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1436
>             Project: Maven Surefire
>          Issue Type: Wish
>    Affects Versions: 2.20, 2.20.1
>            Reporter: Zoltan Haindrich
> earlier...when I've set {{maven.surefire.debug}} while I was using {{-q}}...surefire did show a message that my debugging session is ready to attach we displaying the usual 't e s t s' header nad displaying:
> {code}
> -------------------------------------------------------
>  T E S T S
> -------------------------------------------------------
> Listening for transport dt_socket at address: 5005
> {code}
> since {{2.20}} my terminal is just silent..but, if I connect my debugger after some time...et voila! my debug subject is there waiting in the shadows :)
> running maven without {{-q}} technically makes my terminal history useless...
> possibly connected: showing the executed tests while {{-q}} is active was very handy for me - I often use test patterns like: {{-Dtest=Test*Cli#*\[\*Colum\*\]}}. And knowning that I've hit exactly 0 cases...means I've typoed the pattern - and not passed the cases...

This message was sent by Atlassian JIRA