[JIRA] (JENKINS-56737) Java compiler warnings parser can't cope with Maven timestamps in log

cristalp@java.net (JIRA)

unread,

Mar 25, 2019, 6:05:02 AM3/25/19

to jenkinsc...@googlegroups.com

cristalp created an issue

Jenkins /

JENKINS-56737

Java compiler warnings parser can't cope with Maven timestamps in log

Issue Type:	Bug
Assignee:	Ulli Hafner
Components:	analysis-model-api-plugin
Created:	2019-03-25 10:04
Priority:	Minor
Reporter:	cristalp

We switched on Maven timestamps in our log, since it's a handy way to check build times.

In Maven, this is done by editing conf/logging/simplelogger.properties and setting org.slf4j.simpleLogger.showDateTime=true

This results in compiler warnings like this:

 
                                                                08:52:34.395 [WARNING] /my/path/to/workspace/src/main/java/my/package/TemporalJsonSeqFiling.java:[86,76] redundant cast to long

( given that the date/time format is org.slf4j.simpleLogger.dateTimeFormat=HH:mm:ss.SSS )

Taking a look at the source code, it seems that JAVAC_WARNING_PATTERN does a full match of the line, which does not accept that something could exist before [WARNING] .

We use other parsers for Checkstyle, PMD etc. and they work fine.

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

ullrich.hafner@gmail.com (JIRA)

unread,

Mar 25, 2019, 5:45:02 PM3/25/19

to jenkinsc...@googlegroups.com

Ulli Hafner commented on

JENKINS-56737

Re: Java compiler warnings parser can't cope with Maven timestamps in log

It does allow something in front of [WARNING] but that must be included in brackets. It is quite hard to solve that in general since the logger format could be changed to something completely different...

But I think it should be possible to improve that regex to ignore everything before [WARNING].