Illegal option: -
Usage: jar {ctxui}[vfmn0PMek] [jar-file] [manifest-file] [entry-point] [-C dir] files ...
Options:
    -c  create new archive
    -t  list table of contents for archive
    -x, Extract named (or all) files from the archive.
        If a file with the same name appears more than once in
        the archive, each copy will be extracted, with later copies
        overwriting (replacing) earlier copies unless 'k' is specified.
    -u  update existing archive
    -v  generate verbose output on standard output
    -f  specify archive file name
    -m  include manifest information from specified manifest file
    -n  perform Pack200 normalization after creating a new archive
    -e  specify application entry point for stand-alone application
        bundled into an executable jar file
    -0  store only; use no ZIP compression
    -P  preserve leading '/' (absolute path) and ".." (parent directory) components from file names
    -M  do not create a manifest file for the entries
    -i  generate index information for the specified jar files
    -C  change to the specified directory and include the following file
Operation modifiers valid only in extract mode:
    -k  Do not overwrite existing files.
        If a Jar file entry with the same name exists in the target
        directory, the existing file will not be overwritten.
        As a result, if a file appears more than once in an
        archive, later copies will not overwrite earlier copies.
        Also note that some file system can be case insensitive.
If any file is a directory then it is processed recursively.
The manifest file name, the archive file name and the entry point name are
specified in the same order as the 'm', 'f' and 'e' flags.

Example 1: to archive two class files into an archive called classes.jar:
       jar cvf classes.jar Foo.class Bar.class
Example 2: use an existing manifest file 'mymanifest' and archive all the
           files in the foo/ directory into 'classes.jar':
       jar cvfm classes.jar mymanifest -C foo/ .