[jira] [Resolved] (DAFFODIL-1654) CLI -v option doesn't turn on LogLevel.Info log messaging for parse or unparse, only compile

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

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

Steve Lawrence resolved DAFFODIL-1654.
--------------------------------------
    Fix Version/s: 3.2.0
       Resolution: Fixed

This has been fixed by DAFFODIL-2510 with the change to Log4j, which makes our logging much more consistent across all parts of Daffodil. For example, running with -vv shows debug messages like
{code}
[debug] priorElement = DIComplex(name='file')
{code}
This message comes from the runtime.

> CLI -v option doesn't turn on LogLevel.Info log messaging for parse or unparse, only compile
> --------------------------------------------------------------------------------------------
>
>                 Key: DAFFODIL-1654
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1654
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Back End, CLI, Usability
>    Affects Versions: 2.0.0
>            Reporter: Mike Beckerle
>            Priority: Major
>              Labels: beginner
>             Fix For: 3.2.0
>
>
> I turned on some log messages by changing their level from LogLevel.Debug to LogLevel.Info
> I expected to see them when I did 'daffodil -vv ....' but they did not show up. Lots of messages from the compile phase, but not from the runtime.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)