You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The main method in FeatureFileDumper catches exceptions and writes to System.err but does not exit the process with a non-zero exit code nor throw a RuntimeException. One of these should occur.
Thank you for your report. In processing large databases it's ok to have issues. Stopping the work is not a good idea the, it's better to warn and proceed. The filedumper needs rewokr though.
I agree that sometimes the caller would want problems to be ignored but it
should be up to the caller to do the ignoring (or not ignore). Putting
output to stderr only is not a great way of signaling a problem in my
opinion.
My reading indicates that the consensus for main method usage is to call
System.exit as the main method is expected to be called from scripts rather
than Java code. Scripts can ignore errors if they want to.
On 13 Jan 2015 08:14, "Nickolay V. Shmyrev" [email protected]
wrote:
Thank you for your report. In processing large databases it's ok to have
issues. Stopping the work is not a good idea the, it's better to warn and
proceed. The filedumper needs rewokr though.
—
Reply to this email directly or view it on GitHub #18 (comment).
The main method in
FeatureFileDumper
catches exceptions and writes toSystem.err
but does not exit the process with a non-zero exit code nor throw aRuntimeException
. One of these should occur.The text was updated successfully, but these errors were encountered: