60         \ \ created: {0}
  61 out.extracted=\
  62         extracted: {0}
  63 out.inflated=\
  64         \ \inflated: {0}
  65 out.size=\
  66         (in = {0}) (out= {1})
  67 
  68 usage=\
  69 Usage: jar {ctxui}[vfm0Me] [jar-file] [manifest-file] [entry-point] [-C dir] files ...\n\
  70 Options:\n\
  71 \ \   -c  create new archive\n\
  72 \ \   -t  list table of contents for archive\n\
  73 \ \   -x  extract named (or all) files from archive\n\
  74 \ \   -u  update existing archive\n\
  75 \ \   -v  generate verbose output on standard output\n\
  76 \ \   -f  specify archive file name\n\
  77 \ \   -m  include manifest information from specified manifest file\n\
  78 \ \   -e  specify application entry point for stand-alone application \n\
  79 \ \       bundled into an executable jar file\n\

  80 \ \   -0  store only; use no ZIP compression\n\
  81 \ \   -M  do not create a manifest file for the entries\n\
  82 \ \   -i  generate index information for the specified jar files\n\
  83 \ \   -C  change to the specified directory and include the following file\n\
  84 If any file is a directory then it is processed recursively.\n\
  85 The manifest file name, the archive file name and the entry point name are\n\
  86 specified in the same order as the 'm', 'f' and 'e' flags.\n\n\
  87 Example 1: to archive two class files into an archive called classes.jar: \n\
  88 \ \      jar cvf classes.jar Foo.class Bar.class \n\
  89 Example 2: use an existing manifest file 'mymanifest' and archive all the\n\
  90 \ \          files in the foo/ directory into 'classes.jar': \n\
  91 \ \      jar cvfm classes.jar mymanifest -C foo/ .\n

  60         \ \ created: {0}
  61 out.extracted=\
  62         extracted: {0}
  63 out.inflated=\
  64         \ \inflated: {0}
  65 out.size=\
  66         (in = {0}) (out= {1})
  67 
  68 usage=\
  69 Usage: jar {ctxui}[vfm0Me] [jar-file] [manifest-file] [entry-point] [-C dir] files ...\n\
  70 Options:\n\
  71 \ \   -c  create new archive\n\
  72 \ \   -t  list table of contents for archive\n\
  73 \ \   -x  extract named (or all) files from archive\n\
  74 \ \   -u  update existing archive\n\
  75 \ \   -v  generate verbose output on standard output\n\
  76 \ \   -f  specify archive file name\n\
  77 \ \   -m  include manifest information from specified manifest file\n\
  78 \ \   -e  specify application entry point for stand-alone application \n\
  79 \ \       bundled into an executable jar file\n\
  80 \ \   -p  specify profile name\n\
  81 \ \   -0  store only; use no ZIP compression\n\
  82 \ \   -M  do not create a manifest file for the entries\n\
  83 \ \   -i  generate index information for the specified jar files\n\
  84 \ \   -C  change to the specified directory and include the following file\n\
  85 If any file is a directory then it is processed recursively.\n\
  86 The manifest file name, the archive file name and the entry point name are\n\
  87 specified in the same order as the 'm', 'f' and 'e' flags.\n\n\
  88 Example 1: to archive two class files into an archive called classes.jar: \n\
  89 \ \      jar cvf classes.jar Foo.class Bar.class \n\
  90 Example 2: use an existing manifest file 'mymanifest' and archive all the\n\
  91 \ \          files in the foo/ directory into 'classes.jar': \n\
  92 \ \      jar cvfm classes.jar mymanifest -C foo/ .\n