On 21/06/16 10:16, Andy Seaborne wrote:
An exit code would be good - a contribution maybe?
Recorded as:
https://issues.apache.org/jira/browse/JENA-1197
On 20/06/16 22:06, Jindřich Mynarz wrote:
On Mon, Jun 20, 2016 at 10:39 PM, Andy Seaborne wrote:
Shell magic are be applied:
capture the output and test it.
If in a subshell, the exit here will set the out $?
-
#!/bin/bash
(
X="$(riot --validate ... 2&>1)"
if [[ -n "$X"
On Mon, Jun 20, 2016 at 10:39 PM, Andy Seaborne wrote:
>
> Shell magic are be applied:
>
> capture the output and test it.
>
> If in a subshell, the exit here will set the out $?
>
> -
> #!/bin/bash
>
> (
>X="$(riot --validate ... 2&>1)"
>if [[ -n "$X" ]]
>then
> exit
On 20/06/16 21:15, Jindřich Mynarz wrote:
On Mon, Jun 20, 2016 at 9:54 PM, Andy Seaborne wrote:
The "--validate" is a command line tool for checking data and producing a
report. It does multiple files in one run.
OK, I see. Is there another way to run Riot command line tool so that it
produ
On Mon, Jun 20, 2016 at 9:54 PM, Andy Seaborne wrote:
> The "--validate" is a command line tool for checking data and producing a
> report. It does multiple files in one run.
>
OK, I see. Is there another way to run Riot command line tool so that it
produces an error exit status when provided wi
On 20/06/16 18:17, Jindřich Mynarz wrote:
Hi,
parsing invalid data data with Riot command-line tool (
https://jena.apache.org/documentation/io/#command-line-tools) returns exit
code 0 (i.e. success) instead of an error exit code:
riot --validate invalid.ttl; echo $?
# => 0
Is that an intention
Hi,
parsing invalid data data with Riot command-line tool (
https://jena.apache.org/documentation/io/#command-line-tools) returns exit
code 0 (i.e. success) instead of an error exit code:
riot --validate invalid.ttl; echo $?
# => 0
Is that an intentional design choice?
My Riot version informati
