The $@ option in bash doesn't make sense to come before `generate`
because the only option we can pass before generate cli usage is `help`.
System properties can be passed via JAVA_OPTS, so there's not really a
need for any intermediaries in the command line construction.
Having $@ at the end of the arguments list allows maintainers and users
inspecting options to quickly pass new options to a script. For example,
```
./bin/aspnetcore-petstore.sh --additional-properties sourceFolder=asdf
```
For command line arguments that may appear more than once in the
arguments list, this change doesn't provide any rules about overwriting
values that may exist (hard-coded) in the script. That is, in the
example above, if aspnetcore-petstore.sh already includes the
sourceFolder set to a different value, the "winning" value is up to the
options parser and openapi-generator-cli implementation.
* add run all petstore shell script
* add run all petstore batch file for windows tests
* better output for travis and appveyor
* add shippable config to test all petstore
* show log after test script
* remo all-petstore, update travis build
* update shiippable config
* add run-all-petstore
* failure test using ruby model
* use bash script for run-all-petstore
* update script permission
* fix html batch script
* fix missing doc in jaxrs spec generator
* fix missing api, model test in jaxrs spec generator
* rename licenseInfo for lumen
* remove ruby model failure (for CI test)
* fix "the input line is too long"
* update windows batch file to shorten the commands
* update appveyor config
* update shippable config
* add build script
* update batch file to remove args option
* fix window batch file for spring mvc/boot
* remove logging output to file
