#44 Separate report files (optional)

release_3.2
closed
nobody
None
1
2012-10-10
2002-03-06
Andrey Loskutov
No

We have many wery big projects, and checkstyle make too large report
files (1-10 MB!). It isn't easy to find really poor code from the error
file with >100000 lines...
If we can separate errors by category
(failure/error/warning/info etc), and put this errors to
diferent files, then isn't to match work to find really strong
errors.

Discussion

  • Oliver Burn
    Oliver Burn
    2002-03-07

    Logged In: YES
    user_id=218824

    this could be possible. Two ways to do it not are:
    1) Write another AuditListener
    2) Output errors to an XML file, and then use XSLT to
    seperate.

     
  • Lars Kühne
    Lars Kühne
    2002-03-10

    Logged In: YES
    user_id=401384

    Oliver, I assume you meant "Two ways to do it are".

    I feel this is only possible if we would separate between
    error categories (errors/warnings/...) in the checkstyle
    core. I currently don't see which errors should count as
    "errors" and which errors should count as "warnings".

    Andrei, to get a managable error report I would suggest
    that you turn off the checks that are not relevant to you.
    This way you would simply not generate the files which you
    don't look at anyway. Does that solve your problem or should
    we keep this feature request open?

     
  • Oliver Burn
    Oliver Burn
    2002-03-11

    Logged In: YES
    user_id=218824

    Yes I did mean "Two ways to do it are". Sorry. :-)

     
  • Logged In: YES
    user_id=224122

    May be we should mark up XML message line with "category" attribute for
    better XML+XSL parsing transform capabilities, i.e. "rbrace" or
    "javadoc" or "header".
    Today each message line has only "freetext"
    part, that we could parse.
    This "category" attribute only (placed by
    XML producer), will be solve our problem.

     
  • Rick Giles
    Rick Giles
    2003-07-26

    Logged In: YES
    user_id=539926

    Errors now have source and severity attributes that a
    listener or post-processor such as XSLT for the XML output
    can use to separate them. Recommend closing this request.

     
  • Logged In: YES
    user_id=746148

    Closing this RFE as Rick suggested.