You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2017/11/23 18:16:01 UTC

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

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

Andy Seaborne edited comment on JENA-1434 at 11/23/17 6:15 PM:
---------------------------------------------------------------

If the {{ErrorHandler}} in {{riotcmd}} counts errors and warnings, then it can decide how to set the status code on warnings or errors, by deicing to throw {{CmdException}}.  Then you get all the warnings, not just the first.

{{CmdLangParse.ParseRecord}} could be extended to include the counts and pass out the results and then {{CmdLangParse.outcome(ParseRecord)}} makes a decision.

Warning vs errors is then orthogonal to status code. 

There probably does not need to be a flag for non-zero status code on a warning.


was (Author: andy.seaborne):
If the {{ErrorHandler}} in {{riotcmd}} counts errors and warnings, then it can decide how to set the status code on warnings or errors, by deicing to throw {{CmdException}.  Then you get all the warnings, not just the first.

{{CmdLangParse.ParseRecord}} could be extended to include the counts and pass out the results and then {{CmdLangParse.outcome(ParseRecord)}} makes a decision.


> 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)