* Update JavaJaxRS/resteasy/api.mustache to have swagger annotations
The annotations should now appear on generated resteasy API classes.
* Re-generate resteasy petstore sample
* Add swagger-annotations to rest-easy samples as a dependency
* Regenerat pom.xml and build.gradle files for resteasy
* Properly git-ignore all nbactions.xml files.
* Add a command line action to print the program version (#3892).
I am using maven resource filtering capabilities so that an existing version.properties resource file
gets filtered upon build and populated with the project version tag. This resource is then read
at runtime as required.
* Using a different version tag when unreadable.
* Extended request generation logic with support for serialized body content types other than Json
* Updated the Petstore Python client tests
* Fixed body content type identification for strings
* Fixed errors with cpprest client generation when generating a client that uses arrays of primitive types (vector) and file responses (HttpContent).
* Updated the petstore sample using script.
* Removed debug code.
* Removed extra newline to match master.
* Fixed binary file handling in cpprest. Updated petstore samples.
* Update readme to add Cummins to list
* Cleaning up for pull. Removing unnecessary changes.
* Fixing petstore
* Fixing error in build.
* Fixed error in stream copy for binary data
* Replaced tab with 4 spaces in all modified files.
Replaced tab with 4 spaces in all modified files.
There are several issues with the security policy:
* The security policy is created with `AFSSLPinningModeNone` which means that even if pinned certificates are set (if config.sslCaCert is not nil), they will be ignored. Pinning will not work at all with this security policy.
* The configuration wrapper for the security policy is a bad idea.
* `verifySSL` controls both invalid certificates and domain validation. A vanilla `AFSecurityPolicy` clearly exposes both `allowInvalidCertificates` and `validatesDomainName`.
* `sslCaCert` only allows for a single pinned certificate. A vanilla `AFSecurityPolicy` clearly exposes a set of pinned certificates and makes it very convenient to load them with either `+[AFSecurityPolicy policyWithPinningMode:]` or `+[AFSecurityPolicy certificatesInBundle:]`
Since the security policy does not work at all and adds confusion, it is better to just remove it and let the user configure a security policy that fits their needs.
* fix jaxrs line break
* fix java gradle bat line break
* fix scala gradle line break
* fix undertow crt line break
* fix spring line break
* fix undertow line break in pom
* rollback undertwo petstore to use petstore.yaml
* Removed redundant quotation mark
This additional quotation mark is causing problems in out project and should be removed.
ngrep output:
```
Content-Disposition: form-data; name="file"; filename="file""
..Content-Transfer-Encoding: binary..Content-Type: image/jpg..Content-Length: 27855..........JFIF....
```
* updated petstore sample
* removed line break
