Details
-
Improvement
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
Building Java sources with Maven using org.eclipse.tycho:tycho-compiler-jdt:0.19.0 produces compiler warnings in a slightly different format than older versions:
0.19.0
[WARNING] /path/to/job/job-name/module/src/main/java/com/example/Example.java:[13] something.getOldValue(); ^^^^^^^^^^^^^ The method getOldValue() from the type SomeType is deprecated
before 0.19.0
[WARNING] /path/to/job/job-name/module/src/main/java/com/example/Example.java:[13,0] something.getOldValue(); ^^^^^^^^^^^^^ The method getOldValue() from the type SomeType is deprecated
The only difference is the specification of the location within the source file:
[13] vs. [13,0]
The leads to the problem that when using the "Java Compiler (Eclipse)" parser does not detect any warnings.
When using the "Java Compiler (javac)" parser instead, the warnings are detected but the message is not extracted.
I've already patched the parser and will submit a pull request soon.
Code changed in jenkins
User: Ulli Hafner
Path:
src/main/java/hudson/plugins/warnings/parser/EclipseParser.java
src/test/java/hudson/plugins/warnings/parser/EclipseParserTest.java
src/test/resources/hudson/plugins/warnings/parser/issue21377.txt
http://jenkins-ci.org/commit/warnings-plugin/5e1fc876e584ed7fadfb782367ea99916c8793e3
Log:
Merge pull request #35 from codesimplicity/
JENKINS-21377[FIXED JENKINS-21377] Update of regexp for tycho-compiler-jdt 0.19.0
Compare: https://github.com/jenkinsci/warnings-plugin/compare/f0bfddde1c95...5e1fc876e584