[
https://issues.apache.org/jira/browse/JENA-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16269392#comment-16269392
]
ASF subversion and git services commented on JENA-1434:
-------------------------------------------------------
Commit bb0542eb7474a95cc4c3698ef4e17518dd6210cf in jena's branch
refs/heads/master from [~rvesse]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=bb0542e ]
Rework solution for --stop-warnings (JENA-1434)
- Track total warnings and errors
- Optionally stop on errors and/or warnings
- Report error and warning count as part of statistics
- Always exit non-zero if any errors or warnings are encountered
> 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
> Fix For: Jena 3.6.0
>
>
> 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)
