[
https://issues.apache.org/jira/browse/SUREFIRE-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566771#comment-14566771
]
ASF GitHub Bot commented on SUREFIRE-1158:
------------------------------------------
GitHub user Tibor17 opened a pull request:
https://github.com/apache/maven-surefire/pull/95
[SUREFIRE-1158] Remove console println of TestNG configurator
Some refactoring and implementation for this issue.
These lines are printed with debug (mvn -X) or show-errors (mvn -e):
[INFO] Surefire report directory:
d:\zmaz13\pokus\child\target\surefire-reports
[INFO] Using configured provider
org.apache.maven.surefire.junitcore.JUnitCoreProvider
[INFO] parallel='none', perCoreThreadCount=true, threadCount=0,
useUnlimitedThreads=false, threadCountSuites=0, threadCountClasses=0,
threadCountMethods=0, parallelOptimized=true
Configuring TestNG with: TestNG652Configurator
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Tibor17/maven-surefire s4
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/maven-surefire/pull/95.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #95
----
commit debc688d021243e83aff99c6bdfcb594db52c9b0
Author: Tibor17 <[email protected]>
Date: 2015-05-31T21:41:52Z
[SUREFIRE-1158] Remove console println of TestNG configurator
----
> Remove console println of TestNG configurator
> ---------------------------------------------
>
> Key: SUREFIRE-1158
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1158
> Project: Maven Surefire
> Issue Type: Bug
> Components: TestNG support
> Affects Versions: 2.18.1
> Reporter: Sean Flanigan
> Assignee: Tibor Digana
> Priority: Trivial
>
> When executing TestNG tests, the message
> {{Configuring TestNG with: TestNG652Configurator}}
> appears over and over on the console, even when running {{mvn -q}} (quiet
> mode). This message should probably be turned into a debug-level log
> message. It shouldn't be going directly to stdout.
> See also https://issues.apache.org/jira/browse/SUREFIRE-932
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
