RFE : Executing JCliff on an empty directory should return 0 instead of 1 (error) about jcliff HOT 6 CLOSED

workaround : use empty file with line "{}"

from jcliff.

With RPM_APP_JBOSSCLI_CONF_DIR empty, the argument passed to jcliff is '/*.cliff'. There is nothing I can do to fix this in jcliff. Check empty dir in the calling cmdline.

from jcliff.

why can't we check in the main method whether we have an empty dir or not ?

from jcliff.

The problem is the shell path expansion. If there is no match, the pattern
is passed to jcliff verbatim. That is, if the directory is empty, jcliff
gets '/*.cliff' as the file to process, and when it tries to open that, it
fails.

On Tue, Nov 18, 2014 at 8:57 AM, rbrackma [email protected] wrote:

why can't we check in the main method whether we have an empty dir or not ?

—
Reply to this email directly or view it on GitHub
#25 (comment).

from jcliff.

Note : ${RPM_APP_JBOSSCLI_CONF_DIR} exists, like /tmp/jcliff !
There are simply no .jcliff files in the existing directory.
So I'm passing /tmp/jcliff/.jcliff into jcliff, and that should be caught

from jcliff.

If there are no files there, then what's passed is:

/tmp/jcliff/*.jcliff

jcliff does not expect a pattern there. It expects one of more files. If I
don't return error for this, then I won't be returning an error when you
pass a legitimate file name, but it doesn't exist. This is a problem with
shell processing. *.jcliff is passed verbatim by the shell if nothing
mathches.

On Tue, Nov 18, 2014 at 11:00 AM, rbrackma [email protected] wrote:

Note : ${RPM_APP_JBOSSCLI_CONF_DIR} exists, like /tmp/jcliff !
There are simply no
.jcliff files in the existing directory. So I'm passing /tmp/jcliff/.jcliff
into jcliff, and that should be caught

—
Reply to this email directly or view it on GitHub
#25 (comment).

from jcliff.