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

ASF subversion and git services commented on JENA-1282:
-------------------------------------------------------

Commit 44264d1c5310f7764256cbfee646a165a1e8e2dc in jena's branch 
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=44264d1 ]

JENA-1282: Merge commit 'refs/pull/208/head' of github.com:apache/jena

This closes #208.


> Rename fatal as error in Log support.
> -------------------------------------
>
>                 Key: JENA-1282
>                 URL: https://issues.apache.org/jira/browse/JENA-1282
>             Project: Apache Jena
>          Issue Type: Bug
>    Affects Versions: Jena 3.1.1
>            Reporter: Andy Seaborne
>            Assignee: Andy Seaborne
>            Priority: Minor
>             Fix For: Jena 3.2.0
>
>
> "error" is the more usual naming nowadays. slf4j dos not have a "fatal" 
> level. "fatal" can be taken to indicate that either code can not continue at 
> all but errors in data do not necessarily mean that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to