Using RbUtils Command Line Tools
This page describes how to use RbUtils command line tools and the common options
shared by all these tools.
These command line tools are included in the RbUtils distribution.
Classpath
The easiest way is to include rbutils-all-0.13.jar in the
classpath.
For more information, see the Using RbUtils Tools.
Exit Value
The utility exits with the number of detected errors.
Its also exits with -1 if a parsing problem occurs.
Common Options
The command line usage is (optionnal arguments are between []):
java <classname> \
-r, --root <root> \
[-e, --extension <extension>] \
[-l, --log <type>] \
[-f, --file <file>]
Do not forget the classpath
-
classname - specify the classname of the tool to be used:
org.ktc.rbutils.rb.generation.RbGeneratorCli or
org.ktc.rbutils.rb.check.RbCheckerCli.
-
-r <root> - specify the directory to be
used as root directory for package name resolution. If no -f option is
specified, all files with the -e extension in this directory will be processed.
-
-e <extension> - specify the extension of
the properties source files. Don't include the dot in the extension.
Defaults to properties.
This option is skipped if -f option is on.
-
-l <type> - specify the type of logging and
an optionnal logging file (more than one logger can be specified).
Accepted values are:
- plain for a plain text logging.
- xml for a xml logging.
- quiet do not report anything (only exit
with the number of errors).
Defaults to plain.
Logging file: to specify a logging file, put a ';' after the type of
logging and specify the full path to the logging file.
- plain: if omitted, outputs are displayed
in the console.
- quiet: no effect.
- xml: required.
-
-f, --file <file> - specify the relative
path from root to a properties file to be
processed. This can be used to launch the utility on only one file or on a
limited number of files (use -f option more than once).
