airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Marru (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRAVATA-1240) minor fixups of logging statements
Date Tue, 20 May 2014 04:15:40 GMT

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

Suresh Marru commented on AIRAVATA-1240:
----------------------------------------

Thank you Dave, the patch looks good, will apply it, they were missing the entire stack traces.


While, we greatly appreciate these kind of contributions, just a curiosity question: anything
particular on airavata interested you? Anything we can help navigate? As with with many projects,
the documentation is awful and below par, but is also an active area of improvement. Meanwhile,
please poke the mailing list with any questions. 


> minor fixups of logging statements
> ----------------------------------
>
>                 Key: AIRAVATA-1240
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-1240
>             Project: Airavata
>          Issue Type: Bug
>          Components: Airavata API
>    Affects Versions: 0.11
>            Reporter: Dave Brosius
>            Priority: Trivial
>             Fix For: 0.13
>
>         Attachments: 1240.txt
>
>
> several logger statements pass e.getMessage() as a parm to log.error, without a {} marker,
thus being ignored. Only exceptions are special-handled, so switch to that.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message