[
https://issues.apache.org/jira/browse/UIMA-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577118#action_12577118
]
Jerry Quinn commented on UIMA-853:
----------------------------------
What's a warning in jcasgen? If it prevents jcasgen from writing output, the
tool didn't run properly and should return an error. There's an argument that
anything that causes an exception should be considered an error, unless it's
clear to the code that it can be worked around. Just like with make, if a file
is missing or other equivalent problem, complain and return non-zero.
For starters, actual errors should cause a non-zero return code. Beyond that,
maybe it makes sense to make it an adjustable parameter as to what level of
problem causes failures. For example, gcc has an option to treat warnings as
errors.
As far as the actual return code goes, I don't think it matters too much. As
long as it's documented, you can choose any non-zero value. If you want to be
more sophisticated, you can make different non-zero values mean different
failure modes.
> jcasgen.sh returns success even if the run fails
> ------------------------------------------------
>
> Key: UIMA-853
> URL: https://issues.apache.org/jira/browse/UIMA-853
> Project: UIMA
> Issue Type: Bug
> Components: Tools
> Environment: RHEL 5.1
> IBM Java6
> Reporter: Jerry Quinn
>
> If jcasgen.sh has an error in the input data, it silently fails, returning a
> 0. This means that it cannot behave correctly in a makefile, since the return
> code is completely bogus.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
