[jira] [Updated] (DAFFODIL-889) remove class names from diagnostic messages

["Steve Lawrence (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DAFFODIL-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Lawrence updated DAFFODIL-889:
------------------------------------
    Fix Version/s:     (was: 2.1.0)
                   2.2.0
                   2.2.0

> remove class names from diagnostic messages
> -------------------------------------------
>
>                 Key: DAFFODIL-889
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-889
>             Project: Daffodil
>          Issue Type: Improvement
>          Components: Diagnostics, Usability
>    Affects Versions: s11
>            Reporter: Michael Beckerle
>            Priority: Minor
>             Fix For: 2.2.0
>
>
> In our messages, e.g., this one:
> {code}
> 2013-09-16 09:07:12:254  edu.illinois.ncsa.daffodil.dsom.Include Info[Included schema from file:/home/mbeckerle/git/daffodil-validation-FOUO/vmf/bin/xsd/vmfInternal.dfdl.xsd into namespace urn:vmfDFDLInternal.]
> {code}
> We print a date timestamp, then a class name, then the priority, then the message inside square brackets. 
> The class name is not needed for user-oriented messages, so we should remove it. For aborts and invariant failures and such, the class is perfectly appropriate, but for SDEs, PEs, and their warning counterparts, this adds no value, and pushes the valuable part of the message much further out to the right where it is sometimes harder to read.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)