Tell users a mistake is present when parameters are incorrect/unknown

[Famlam]

I'm calling JSCover like this from the command line (Windows):
java -jar "...\JSCover-all.jar" -ws --unknownoption --report-dir="..." --no-instrument="..."

The text I see after that is the following:

Usage: java -jar JSCover-all.jar -ws [OPTION]...
Run a server for instrumenting JavaScript with code coverage information.

Options:
      --document-root=DIR       serve content from DIR (default: current directory)
      --no-instrument=URL       do not instrument URL
      --no-instrument-reg=URL   do not instrument if URL matches regular expression
      --only-instrument-reg=URL only instrument if URL matches regular expression
      --report-dir=DIR          store report to DIR (default: current directory)
      --port=PORT               use PORT for TCP port (default: 8080)
      --proxy                   run as a proxy
      --js-version=VERSION      JavaScript version 1.0, 1.2, ..., 1.8 (default: 1.3)
      --no-branch               turn off branch coverage data collection
      --no-function             turn off function coverage data collection
      --include-unloaded-js     include unloaded JavaScript under <document-root> in the report
      --log=LEVEL               set logging level to: SEVERE (default), WARNING, INFO, CONFIG, FINE, FINER, FINEST
  -h, --help                    display this help and exit

This text does not explain to me why I'm seeing the message, instead of the expected output. In fact, there isn't even a line that tells me I did make a mistake, and therefore see this text. It would be great if a line could be added, explaining why I'm seeing this message. For example: There is no option '--unknownoption'

[tntim96]

I've checked a fix into trunk. Are you able to checkout, build the JAR and re-try?

[Famlam]

I'm sorry, but I don't know how to build Java applications :(

[devangnegandhi]

Well since @Famlam does'nt know how to build jscover and I had already built jscover to verify another feature for @tntim96, I have verified that this change has been fixed. You can close this issue.

[tntim96]

Thanks