You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@daffodil.apache.org by "Steve Lawrence (Jira)" <ji...@apache.org> on 2022/02/01 16:13:00 UTC

[jira] [Commented] (DAFFODIL-2642) Daffodil Resolver - logging as info should be log4j "error"

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

Steve Lawrence commented on DAFFODIL-2642:
------------------------------------------

Shouldn't failure to resovle errors show up as SDEs rather than as log messages? That way they end up in compile result diagnostics?

> Daffodil Resolver - logging as info should be log4j "error"
> -----------------------------------------------------------
>
>                 Key: DAFFODIL-2642
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2642
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Front End
>    Affects Versions: 3.2.1
>            Reporter: Mike Beckerle
>            Priority: Major
>
> There are a couple places in the Resolver where we used to log at INFO level, which used to be displayed by default. Those were changed to log4j "info" during our update to use log4j, but log4j "info" doesn't display by default, only "error" displays by default. 
> So these should be changed to log.error calls. 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)