Phenomenon: mvn test the implementation process, will continue to print the debug log http client
directly to the conclusion: the problem is the reason mvn test plus debugging parameters -X, remove enough; online to a bunch of configuration does not apply here.
Background
maven project introduced HttpClient
do not know when to begin, each jenkins execute all print debug log pile, it is affecting the normal log output:
Debugging process
Online search a bunch of data, the solutions are to be configured, such as the configuration logback.xml, configure the log4j.properties; these programs are tested can not solve the problem.
Occasionally time that the local implementation of mvn test does not print log and found that the commands executed on the platform a bit different, with the command of the platform: mvn test -X -B -e -U -Dmaven.compile.fork = true. The fundamental reason is found, because the addition of -X parameters, debug mode, debug log into a lot.
