maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michal Kordas (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (MCHECKSTYLE-291) Change format of violation message
Date Mon, 27 Apr 2015 20:24:38 GMT

    [ https://issues.apache.org/jira/browse/MCHECKSTYLE-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14514907#comment-14514907
] 

Michal Kordas edited comment on MCHECKSTYLE-291 at 4/27/15 8:23 PM:
--------------------------------------------------------------------

It works in IntelliJ when searching by {{CTRL}}+{{N}}, so the guys probably took this convention
from somewhere.


was (Author: mkordas):
It works in IntelliJ when searching by {{CTRL}}+{{{N}}, so the guys probably took this convention
from somewhere.

> Change format of violation message
> ----------------------------------
>
>                 Key: MCHECKSTYLE-291
>                 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-291
>             Project: Maven Checkstyle Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.15
>            Reporter: Michal Kordas
>            Assignee: Michael Osipov
>
> For example on LineLength violation in console I get the following error:
> _\[ERROR] src\test\java\com\test\SampleTest.java *\[89]* (sizes) LineLength: Line is
longer than 180 characters (found 202)._
> It would be better to have colon and line number instead of braces, so that I can directly
paste the reference to IntelliJ and go to affected line:
> _\[ERROR] src\test\java\com\test\SampleTest.java *:89* (sizes) LineLength: Line is longer
than 180 characters (found 202)._
> The same format has exception stacktrace in Java.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message