Logging level under maven surefire

Question

I'm unable to adjust java logging's logging level. I'm using maven surefire (mvn test), and trying to adjust from the default INFO to e.g. FINEST.

I have logging.properties file under src/test/resources/logging.properties

after compile, i see under target/test-classes, i see a logging.properties file with the intended config:

java.util.logging.ConsoleHandler.level=FINEST

javax.enterprise.system.container.ejb.level=FINE

...

however the console output from glassfish only have INFO / SEVERE level messages.

Where did I go wrong? or is this another pain in the butt thing with maven?

I'm a bit confused here. How does glassfish fit into this? I think it's likely you are getting confused between glassfish's logging and the maven unit test logging. What framework is the maven build using for logging? — drekka, Oct 15 '10 at 02:35
i'm debugging a unit test that uses the Embedded container in glassfish v3. according to: http://forums.java.net/jive/thread.jspa?messageID=395759, under reply by 'Marina Vatkina', thats the key to output FINE messages for the EJB container... I guess my question is is my setup correct for java util logging? Or is there extra configuration needed? - not just for this particular instance, but lets say I have a class com.something.Main, and i want to output FINEST messages for it... — Dzhu, Oct 15 '10 at 03:30

score 19 · Answer 1 · edited Jun 23 '22 at 10:37

19

I tried setting java.util.logging.config.file in the MAVEN_OPTS environment variable, which does not work but finally got it working by putting that system property in the pom.xml (and of course creating an appropriate logging.properties in src/test/resources):

    <plugins>
      <plugin>
        <artifactId>maven-surefire-plugin</artifactId>
        <configuration>
           <systemProperties>
             <property> 
               <name>java.util.logging.config.file</name>
               <value>src/test/resources/logging.properties</value>
             </property>
           </systemProperties>
        </configuration>
      </plugin>
    </plugins>

edited Jun 23 '22 at 10:37

Sergey Vyacheslavovich Brunov

17,291
7
48
81

answered Sep 05 '12 at 07:54

ehrencrona

6,102
1
18
24

2

Setting `-Djava.util.logging.config.file` on the maven command line did not work for me, but this did. – slevin Nov 25 '14 at 21:22
2

Because surefire plugin do not propogate all system properties you passed to maven one the command line to actual unit test executor – Oleksandr Pryimak Oct 14 '15 at 13:12

score 10 · Accepted Answer · edited Mar 06 '15 at 15:17

10

You need to specifiy your handlers in the logging file

handlers = java.util.logging.ConsoleHandler, java.util.logging.FileHandler

then it should work

edited Mar 06 '15 at 15:17

zb226

9,586
6
49
79

answered Oct 22 '10 at 18:41

martin

116
1
2

which file? and what about a log4j.xml file syntax? – Pipo Aug 16 '21 at 23:15

score 3 · Answer 3 · answered Jul 27 '11 at 17:40

try

${build.testOutputDirectory}/logging.properties

Also, I specify this stuff on the command line with surfire-args.

<argLine>${surefire.argLine} ${argLine} -Djava.util.logging.config.file=${build.testOutputDirectory}/logging.properties</argLine>

score 2 · Answer 4 · answered Aug 08 '14 at 10:32

I was looking at this exact issue, but did not want a project configuration (pom.xml) file change for every time I need specific logging on a test.

The -D property works from maven command line.

Thus you can select the logging configuration file from the command line:

mvn -Djava.util.logging.config.file=`enter filename here` test

If you are using the generic level denominator .level=FINEST be aware that 3rd party logging will also appear at that level.

To disable or set the maven or 3rd party logging to a specific level use explicit log level selection for those classes in the selected log configuration file.

I have a lot of log lines from com.google.inject.....

aug 08, 2014 12:14:33 PM com.google.inject.internal.util.$Stopwatch resetAndLog
FINE: Instance member validation: 3ms
aug 08, 2014 12:14:33 PM com.google.inject.internal.util.$Stopwatch resetAndLog
FINE: Provider verification: 1ms
aug 08, 2014 12:14:33 PM com.google.inject.internal.util.$Stopwatch resetAndLog
FINE: Static member injection: 1ms

So I add:

com.google.inject.level=INFO

to the file. Remember that the level setting is recursive to all subclasses. Thus com.level=NONE will disable all logging for all loggers from the com domain.

Combining this with the test select feature -Dtest=... in the surefire plugin described here is very good for isolating bugs and errors.

Logging level under maven surefire

4 Answers4

Linked