[jira] [Reopened] (JENA-1434) Allow warnings to be treated as errors by RIOT

["Rob Vesse (JIRA)" <ji...@apache.org>]

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

Rob Vesse reopened JENA-1434:
-----------------------------

Reopening, while {{--stop}} works for errors it does not work for warnings.  It is not unreasonable to want to allow warnings to be treated as errors

> Allow warnings to be treated as errors by RIOT
> ----------------------------------------------
>
>                 Key: JENA-1434
>                 URL: https://issues.apache.org/jira/browse/JENA-1434
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: RIOT
>    Affects Versions: Jena 3.5.0
>            Reporter: Ian Dickinson
>            Assignee: Rob Vesse
>
> I would like to use `riot --validate` as part of an integration test for a system that generates Turtle. Ideally, the exit status for the riot command would be non-zero, indicating a problem, if the input was not valid. However, I see an exit status of zero always:
> {noformat}
> $ riot --validate alert.ttl && echo 'exit status is: ' $?
> 13:50:37 WARN  riot                 :: [line: 39, col: 25] Lexical form '2017-03-19T00:00:00+00:00' not valid for datatype XSD date
> 13:50:37 WARN  riot                 :: [line: 42, col: 20] Lexical form '' not valid for datatype XSD date
> 13:50:37 WARN  riot                 :: [line: 58, col: 20] Lexical form '' not valid for datatype XSD date
> exit status is:  0
> {noformat}
> Version info:
> {noformat}
> $ riot --version
> Jena:       VERSION: 3.5.0
> Jena:       BUILD_DATE: 2017-10-30T09:20:28+0000
> RIOT:       VERSION: 3.5.0
> RIOT:       BUILD_DATE: 2017-10-30T09:20:28+0000
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)