Update swagger-parser-version to 2.0.13-OpenAPITools.org-1

[jmini]

PR checklist

• Read the contribution guidelines.
• Ran the shell script under ./bin/ to update Petstore sample so that CIs can verify the change. (For instance, only need to run ./bin/{LANG}-petstore.sh, ./bin/openapi3/{LANG}-petstore.sh if updating the {LANG} (e.g. php, ruby, python, etc) code generator or {LANG} client's mustache templates). Windows batch files can be found in .\bin\windows\.
• Filed the PR against the correct branch: master, 3.4.x, 4.0.x. Default: master.
• Copied the technical committee to review the pull request if your PR is targeting a particular programming language.

Description of the PR

Update the Swagger-Parser version to 2.0.13-OpenAPITools.org-1

[jmini]

This line must be removed when we switch to a release version!

[jmini]

WIP:
For the moment trying a 2.0.13-SNAPSHOT version.
If everything goes well I will publish a 2.0.13-OpenAPITools.org-1 release.

[jmini]

I have fixed 2 tests in InlineModelResolverTest in e4b5ece

The Parser behave differently:

• arbitraryObjectResponseWithAdditionalProperty:
  • mediaType.getSchema() returns a MapSchema instead of a ObjectSchema => this is correct.
• resolveInlineObjectResponseWithAdditionalProperties:
  • mediaType.getSchema().getAdditionalProperties() returns a Schema with a $ref instead of the ObjectSchema
  • ModelUtils.getReferencedSchema can be used.
  • The referenced schema is a Schema and not an ObjectSchema

If our CI Tests do not detect more regression, I propose to continue with our release of Swagger-Parser.

[jmini]

The samples were no longer up-to-date. I have pushed 3c18263 to fix this

We see some changes with Integer that becomes Object in enums.

Example

--- a/samples/server/petstore/jaxrs-jersey/src/gen/java/org/openapitools/model/EnumTest.java
+++ b/samples/server/petstore/jaxrs-jersey/src/gen/java/org/openapitools/model/EnumTest.java
@@ -107,13 +107,13 @@ public class EnumTest   {
    * Gets or Sets enumInteger
    */
   public enum EnumIntegerEnum {
-    NUMBER_1(1),
+    _1("1"),
     
-    NUMBER_MINUS_1(-1);
+    _1("-1");
 
-    private Integer value;
+    private Object value;
 
-    EnumIntegerEnum(Integer value) {
+    EnumIntegerEnum(Object value) {
       this.value = value;
     }
 
@@ -124,7 +124,7 @@ public class EnumTest   {
     }
 
     @JsonCreator
-    public static EnumIntegerEnum fromValue(Integer value) {
+    public static EnumIntegerEnum fromValue(Object value) {
       for (EnumIntegerEnum b : EnumIntegerEnum.values()) {
         if (b.value.equals(value)) {
           return b;

We need to investigate, because I think that this is not OK.
(the required fix might be in Swagger-Parser or in OpenAPI Generator)

[jmini]

I found the reason for the regression we observe:
swagger-api/swagger-parser#1090

This needs to be fixed before we can update Swagger-Parser

cc: @cvgaviao

[jmini]

Now that 2.0.13-OpenAPITools.org-1 is released to Maven Central, this PR can use this version and is no longer WIP.

[wing328]

LGTM