Re: [basex-talk] handling corrupt files during import (was: Re: adding zip contents – bug or feature?)

Currently basexclient doesn’t exit with an error code (≠0) when it encounters a file that throws an exception on the server side during import. This is unfortunate in our use case where we issue several svn checkout and BaseX ADD statements in a Makefile. Since there is no non-null exit status, make will always continue, and the errors will not be dealt with unless someone watches the process closely.

This has now been resolved for all command-line APIs; note that the Windows batch scripts (basex.bat, etc) were updated as well.

Christian