[ 
https://issues.jenkins-ci.org/browse/JENKINS-12482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158744#comment-158744
 ] 

Ulli Hafner commented on JENKINS-12482:
---------------------------------------

Ok, I see. Seems that I need to add an additional parser for Java 7 (or extend 
the current one). Can you please attach the warnings from your comment above as 
a file? Seems that not all white space characters are preserved in the comment.
                
> Warnings not detected when file path does not appear after [WARNING]
> --------------------------------------------------------------------
>
>                 Key: JENKINS-12482
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12482
>             Project: Jenkins
>          Issue Type: Bug
>          Components: warnings
>    Affects Versions: current
>         Environment: ubuntu, java 1.7.0_02, tomcat7, jenkins 1.447, warnings 
> plugin v3.26, maven-compiler-plugin v2.3.2
>            Reporter: Stefan Thurnherr
>            Assignee: Ulli Hafner
>
> When compiling a Java project using the javac compiler, most of the warnings 
> in my console log appear as follows:
> {noformat}
> [WARNING]     BasicTableInfo
> /absolute/path/to/source/File.java:[143,66] [unchecked] unchecked conversion
> {noformat}
> and are thus not picked up by the warnings plugin.
> When there is no additional token before the source file path, such as in the 
> following warning:
> {noformat}
> [WARNING] /absolute/path/to/source/File.java:[181,69] [unchecked] unchecked 
> cast
> {noformat}
> then the warning is correctly picked up by the warnings plugin.
> Btw: Coloring in the console log has the same "bug": when the path appears as 
> the first token (after [WARNING]), then the path and the next token (warning 
> category) are highlighted in dark-yellow. When there is an additional token 
> before the path, only that additional token is highlighted in dark-yellow 
> (not the path and subsequent tokens).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to