[JAXRS-spec] Add option useSwaggerAnnotations (for MicroProfile-OpenAPI) by michbeck100 · Pull Request #813 · OpenAPITools/openapi-generator

michbeck100 · 2018-08-14T11:47:34Z

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 and ./bin/security/{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.3.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

The Microprofile OpenAPI specification allows to have just a static openapi.yaml file in the application module’s root META-INF folder (see here). So this PR adds an additional property "useSwaggerAnnotations" that doesn't generate the Swagger annotations if set to false (default value is true for backward compatibility).

This way you can easily generate code that conforms to contract first and is compliant with the microprofile openapi specification

…in generated code. By default annotations are generated.

…(..) is too early

# Conflicts: # modules/openapi-generator/src/main/java/org/openapitools/codegen/languages/JavaJAXRSSpecServerCodegen.java

jmini · 2018-08-15T05:23:04Z

Thank you for this PR. I like your approach.

Shippable — Run 2208 status is FAILED.

The Shippable CI Job ensure that the content of the samples/ folder correspond to the state of the generator. Can you please update it?

Run mvn to update the cli
Run the scripts to udpate the outdated samples:
- bin/jaxrs-cxf-cdi-petstore-server.sh to update samples/server/petstore/jaxrs-cxf-cdi
- bin/jaxrs-spec-petstore-server-interface.sh to update samples/server/petstore/jaxrs-spec-interface
- bin/jaxrs-spec-petstore-server.sh to update samples/server/petstore/jaxrs-spec
add the changes as new commit in this PR (we will squash all small commit of the PR as one single commit when we merge it)

See also: https://github.com/OpenAPITools/openapi-generator/wiki/Pull-Request-Checklist#shippable-ensure-up-to-date

… filter_swagger_annotations

michbeck100 · 2018-08-15T05:46:18Z

I just ran bin/jaxrs-spec-petstore-server.sh, my fault. How can one know which scripts to run?

jmini · 2018-08-15T05:53:24Z

I once generated this table: https://github.com/OpenAPITools/openapi-generator/wiki/Samples-folder#scripts (might be outdated)

I have computed the list for your by looking at the Shippable error report.

If you have time (takes some minutes), you can also run bin/utils/ensure-up-to-date locally.

michbeck100 · 2018-08-15T08:03:58Z

I had to fix some missing imports in efe7014. BTW: it seems that before 82eba8d this wan't working at all. And i don't really know what this is good for.

jmini · 2018-08-15T16:05:56Z

Thank you a lot for this contribution

wing328 · 2018-08-22T13:10:21Z

@michbeck100 thanks for the enhancement, which is included in the v3.2.2 stable release: https://twitter.com/oas_generator/status/1032252335131512832

michbeck100 · 2018-08-14T11:47:34Z

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 and ./bin/security/{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.3.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

The Microprofile OpenAPI specification allows to have just a static openapi.yaml file in the application module’s root META-INF folder (see here). So this PR adds an additional property "useSwaggerAnnotations" that doesn't generate the Swagger annotations if set to false (default value is true for backward compatibility).

This way you can easily generate code that conforms to contract first and is compliant with the microprofile openapi specification

…in generated code. By default annotations are generated.

…(..) is too early

# Conflicts: # modules/openapi-generator/src/main/java/org/openapitools/codegen/languages/JavaJAXRSSpecServerCodegen.java

jmini · 2018-08-15T05:23:04Z

Thank you for this PR. I like your approach.

Shippable — Run 2208 status is FAILED.

The Shippable CI Job ensure that the content of the samples/ folder correspond to the state of the generator. Can you please update it?

Run mvn to update the cli
Run the scripts to udpate the outdated samples:
- bin/jaxrs-cxf-cdi-petstore-server.sh to update samples/server/petstore/jaxrs-cxf-cdi
- bin/jaxrs-spec-petstore-server-interface.sh to update samples/server/petstore/jaxrs-spec-interface
- bin/jaxrs-spec-petstore-server.sh to update samples/server/petstore/jaxrs-spec
add the changes as new commit in this PR (we will squash all small commit of the PR as one single commit when we merge it)

See also: https://github.com/OpenAPITools/openapi-generator/wiki/Pull-Request-Checklist#shippable-ensure-up-to-date

… filter_swagger_annotations

michbeck100 · 2018-08-15T05:46:18Z

I just ran bin/jaxrs-spec-petstore-server.sh, my fault. How can one know which scripts to run?

jmini · 2018-08-15T05:53:24Z

I once generated this table: https://github.com/OpenAPITools/openapi-generator/wiki/Samples-folder#scripts (might be outdated)

I have computed the list for your by looking at the Shippable error report.

If you have time (takes some minutes), you can also run bin/utils/ensure-up-to-date locally.

michbeck100 · 2018-08-15T08:03:58Z

I had to fix some missing imports in efe7014. BTW: it seems that before 82eba8d this wan't working at all. And i don't really know what this is good for.

jmini · 2018-08-15T16:05:56Z

Thank you a lot for this contribution

wing328 · 2018-08-22T13:10:21Z

@michbeck100 thanks for the enhancement, which is included in the v3.2.2 stable release: https://twitter.com/oas_generator/status/1032252335131512832

michbeck100 · 2018-08-14T11:47:34Z

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 and ./bin/security/{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.3.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

The Microprofile OpenAPI specification allows to have just a static openapi.yaml file in the application module’s root META-INF folder (see here). So this PR adds an additional property "useSwaggerAnnotations" that doesn't generate the Swagger annotations if set to false (default value is true for backward compatibility).

This way you can easily generate code that conforms to contract first and is compliant with the microprofile openapi specification

…in generated code. By default annotations are generated.

…(..) is too early

# Conflicts: # modules/openapi-generator/src/main/java/org/openapitools/codegen/languages/JavaJAXRSSpecServerCodegen.java

jmini · 2018-08-15T05:23:04Z

Thank you for this PR. I like your approach.

Shippable — Run 2208 status is FAILED.

The Shippable CI Job ensure that the content of the samples/ folder correspond to the state of the generator. Can you please update it?

Run mvn to update the cli
Run the scripts to udpate the outdated samples:
- bin/jaxrs-cxf-cdi-petstore-server.sh to update samples/server/petstore/jaxrs-cxf-cdi
- bin/jaxrs-spec-petstore-server-interface.sh to update samples/server/petstore/jaxrs-spec-interface
- bin/jaxrs-spec-petstore-server.sh to update samples/server/petstore/jaxrs-spec
add the changes as new commit in this PR (we will squash all small commit of the PR as one single commit when we merge it)

See also: https://github.com/OpenAPITools/openapi-generator/wiki/Pull-Request-Checklist#shippable-ensure-up-to-date

… filter_swagger_annotations

michbeck100 · 2018-08-15T05:46:18Z

I just ran bin/jaxrs-spec-petstore-server.sh, my fault. How can one know which scripts to run?

jmini · 2018-08-15T05:53:24Z

I once generated this table: https://github.com/OpenAPITools/openapi-generator/wiki/Samples-folder#scripts (might be outdated)

I have computed the list for your by looking at the Shippable error report.

If you have time (takes some minutes), you can also run bin/utils/ensure-up-to-date locally.

michbeck100 · 2018-08-15T08:03:58Z

I had to fix some missing imports in efe7014. BTW: it seems that before 82eba8d this wan't working at all. And i don't really know what this is good for.

jmini · 2018-08-15T16:05:56Z

Thank you a lot for this contribution

wing328 · 2018-08-22T13:10:21Z

@michbeck100 thanks for the enhancement, which is included in the v3.2.2 stable release: https://twitter.com/oas_generator/status/1032252335131512832

michbeck100 · 2018-08-14T11:47:34Z

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 and ./bin/security/{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.3.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

The Microprofile OpenAPI specification allows to have just a static openapi.yaml file in the application module’s root META-INF folder (see here). So this PR adds an additional property "useSwaggerAnnotations" that doesn't generate the Swagger annotations if set to false (default value is true for backward compatibility).

This way you can easily generate code that conforms to contract first and is compliant with the microprofile openapi specification

…in generated code. By default annotations are generated.

…(..) is too early

# Conflicts: # modules/openapi-generator/src/main/java/org/openapitools/codegen/languages/JavaJAXRSSpecServerCodegen.java

jmini · 2018-08-15T05:23:04Z

Thank you for this PR. I like your approach.

Shippable — Run 2208 status is FAILED.

The Shippable CI Job ensure that the content of the samples/ folder correspond to the state of the generator. Can you please update it?

Run mvn to update the cli
Run the scripts to udpate the outdated samples:
- bin/jaxrs-cxf-cdi-petstore-server.sh to update samples/server/petstore/jaxrs-cxf-cdi
- bin/jaxrs-spec-petstore-server-interface.sh to update samples/server/petstore/jaxrs-spec-interface
- bin/jaxrs-spec-petstore-server.sh to update samples/server/petstore/jaxrs-spec
add the changes as new commit in this PR (we will squash all small commit of the PR as one single commit when we merge it)

See also: https://github.com/OpenAPITools/openapi-generator/wiki/Pull-Request-Checklist#shippable-ensure-up-to-date

… filter_swagger_annotations

michbeck100 · 2018-08-15T05:46:18Z

I just ran bin/jaxrs-spec-petstore-server.sh, my fault. How can one know which scripts to run?

jmini · 2018-08-15T05:53:24Z

I once generated this table: https://github.com/OpenAPITools/openapi-generator/wiki/Samples-folder#scripts (might be outdated)

I have computed the list for your by looking at the Shippable error report.

If you have time (takes some minutes), you can also run bin/utils/ensure-up-to-date locally.

michbeck100 · 2018-08-15T08:03:58Z

I had to fix some missing imports in efe7014. BTW: it seems that before 82eba8d this wan't working at all. And i don't really know what this is good for.

jmini · 2018-08-15T16:05:56Z

Thank you a lot for this contribution

wing328 · 2018-08-22T13:10:21Z

@michbeck100 thanks for the enhancement, which is included in the v3.2.2 stable release: https://twitter.com/oas_generator/status/1032252335131512832

michbeck100 · 2018-08-14T11:47:34Z

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 and ./bin/security/{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.3.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

The Microprofile OpenAPI specification allows to have just a static openapi.yaml file in the application module’s root META-INF folder (see here). So this PR adds an additional property "useSwaggerAnnotations" that doesn't generate the Swagger annotations if set to false (default value is true for backward compatibility).

This way you can easily generate code that conforms to contract first and is compliant with the microprofile openapi specification

…in generated code. By default annotations are generated.

…(..) is too early

# Conflicts: # modules/openapi-generator/src/main/java/org/openapitools/codegen/languages/JavaJAXRSSpecServerCodegen.java

jmini · 2018-08-15T05:23:04Z

Thank you for this PR. I like your approach.

Shippable — Run 2208 status is FAILED.

The Shippable CI Job ensure that the content of the samples/ folder correspond to the state of the generator. Can you please update it?

Run mvn to update the cli
Run the scripts to udpate the outdated samples:
- bin/jaxrs-cxf-cdi-petstore-server.sh to update samples/server/petstore/jaxrs-cxf-cdi
- bin/jaxrs-spec-petstore-server-interface.sh to update samples/server/petstore/jaxrs-spec-interface
- bin/jaxrs-spec-petstore-server.sh to update samples/server/petstore/jaxrs-spec
add the changes as new commit in this PR (we will squash all small commit of the PR as one single commit when we merge it)

See also: https://github.com/OpenAPITools/openapi-generator/wiki/Pull-Request-Checklist#shippable-ensure-up-to-date

… filter_swagger_annotations

michbeck100 · 2018-08-15T05:46:18Z

I just ran bin/jaxrs-spec-petstore-server.sh, my fault. How can one know which scripts to run?

jmini · 2018-08-15T05:53:24Z

I once generated this table: https://github.com/OpenAPITools/openapi-generator/wiki/Samples-folder#scripts (might be outdated)

I have computed the list for your by looking at the Shippable error report.

If you have time (takes some minutes), you can also run bin/utils/ensure-up-to-date locally.

michbeck100 · 2018-08-15T08:03:58Z

I had to fix some missing imports in efe7014. BTW: it seems that before 82eba8d this wan't working at all. And i don't really know what this is good for.

jmini · 2018-08-15T16:05:56Z

Thank you a lot for this contribution

wing328 · 2018-08-22T13:10:21Z

@michbeck100 thanks for the enhancement, which is included in the v3.2.2 stable release: https://twitter.com/oas_generator/status/1032252335131512832

michbeck100 · 2018-08-14T11:47:34Z

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 and ./bin/security/{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.3.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

The Microprofile OpenAPI specification allows to have just a static openapi.yaml file in the application module’s root META-INF folder (see here). So this PR adds an additional property "useSwaggerAnnotations" that doesn't generate the Swagger annotations if set to false (default value is true for backward compatibility).

This way you can easily generate code that conforms to contract first and is compliant with the microprofile openapi specification

…in generated code. By default annotations are generated.

…(..) is too early

# Conflicts: # modules/openapi-generator/src/main/java/org/openapitools/codegen/languages/JavaJAXRSSpecServerCodegen.java

jmini · 2018-08-15T05:23:04Z

Thank you for this PR. I like your approach.

Shippable — Run 2208 status is FAILED.

The Shippable CI Job ensure that the content of the samples/ folder correspond to the state of the generator. Can you please update it?

Run mvn to update the cli
Run the scripts to udpate the outdated samples:
- bin/jaxrs-cxf-cdi-petstore-server.sh to update samples/server/petstore/jaxrs-cxf-cdi
- bin/jaxrs-spec-petstore-server-interface.sh to update samples/server/petstore/jaxrs-spec-interface
- bin/jaxrs-spec-petstore-server.sh to update samples/server/petstore/jaxrs-spec
add the changes as new commit in this PR (we will squash all small commit of the PR as one single commit when we merge it)

See also: https://github.com/OpenAPITools/openapi-generator/wiki/Pull-Request-Checklist#shippable-ensure-up-to-date

… filter_swagger_annotations

michbeck100 · 2018-08-15T05:46:18Z

I just ran bin/jaxrs-spec-petstore-server.sh, my fault. How can one know which scripts to run?

jmini · 2018-08-15T05:53:24Z

I once generated this table: https://github.com/OpenAPITools/openapi-generator/wiki/Samples-folder#scripts (might be outdated)

I have computed the list for your by looking at the Shippable error report.

If you have time (takes some minutes), you can also run bin/utils/ensure-up-to-date locally.

michbeck100 · 2018-08-15T08:03:58Z

I had to fix some missing imports in efe7014. BTW: it seems that before 82eba8d this wan't working at all. And i don't really know what this is good for.

jmini · 2018-08-15T16:05:56Z

Thank you a lot for this contribution

wing328 · 2018-08-22T13:10:21Z

@michbeck100 thanks for the enhancement, which is included in the v3.2.2 stable release: https://twitter.com/oas_generator/status/1032252335131512832

michbeck100 · 2018-08-14T11:47:34Z

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 and ./bin/security/{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.3.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

The Microprofile OpenAPI specification allows to have just a static openapi.yaml file in the application module’s root META-INF folder (see here). So this PR adds an additional property "useSwaggerAnnotations" that doesn't generate the Swagger annotations if set to false (default value is true for backward compatibility).

This way you can easily generate code that conforms to contract first and is compliant with the microprofile openapi specification

…in generated code. By default annotations are generated.

…(..) is too early

# Conflicts: # modules/openapi-generator/src/main/java/org/openapitools/codegen/languages/JavaJAXRSSpecServerCodegen.java

jmini · 2018-08-15T05:23:04Z

Thank you for this PR. I like your approach.

Shippable — Run 2208 status is FAILED.

The Shippable CI Job ensure that the content of the samples/ folder correspond to the state of the generator. Can you please update it?

Run mvn to update the cli
Run the scripts to udpate the outdated samples:
- bin/jaxrs-cxf-cdi-petstore-server.sh to update samples/server/petstore/jaxrs-cxf-cdi
- bin/jaxrs-spec-petstore-server-interface.sh to update samples/server/petstore/jaxrs-spec-interface
- bin/jaxrs-spec-petstore-server.sh to update samples/server/petstore/jaxrs-spec
add the changes as new commit in this PR (we will squash all small commit of the PR as one single commit when we merge it)

See also: https://github.com/OpenAPITools/openapi-generator/wiki/Pull-Request-Checklist#shippable-ensure-up-to-date

… filter_swagger_annotations

michbeck100 · 2018-08-15T05:46:18Z

I just ran bin/jaxrs-spec-petstore-server.sh, my fault. How can one know which scripts to run?

jmini · 2018-08-15T05:53:24Z

I once generated this table: https://github.com/OpenAPITools/openapi-generator/wiki/Samples-folder#scripts (might be outdated)

I have computed the list for your by looking at the Shippable error report.

If you have time (takes some minutes), you can also run bin/utils/ensure-up-to-date locally.

michbeck100 · 2018-08-15T08:03:58Z

I had to fix some missing imports in efe7014. BTW: it seems that before 82eba8d this wan't working at all. And i don't really know what this is good for.

jmini · 2018-08-15T16:05:56Z

Thank you a lot for this contribution

wing328 · 2018-08-22T13:10:21Z

@michbeck100 thanks for the enhancement, which is included in the v3.2.2 stable release: https://twitter.com/oas_generator/status/1032252335131512832

michbeck100 · 2018-08-14T11:47:34Z

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 and ./bin/security/{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.3.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

The Microprofile OpenAPI specification allows to have just a static openapi.yaml file in the application module’s root META-INF folder (see here). So this PR adds an additional property "useSwaggerAnnotations" that doesn't generate the Swagger annotations if set to false (default value is true for backward compatibility).

This way you can easily generate code that conforms to contract first and is compliant with the microprofile openapi specification

…in generated code. By default annotations are generated.

…(..) is too early

# Conflicts: # modules/openapi-generator/src/main/java/org/openapitools/codegen/languages/JavaJAXRSSpecServerCodegen.java

jmini · 2018-08-15T05:23:04Z

Thank you for this PR. I like your approach.

Shippable — Run 2208 status is FAILED.

The Shippable CI Job ensure that the content of the samples/ folder correspond to the state of the generator. Can you please update it?

Run mvn to update the cli
Run the scripts to udpate the outdated samples:
- bin/jaxrs-cxf-cdi-petstore-server.sh to update samples/server/petstore/jaxrs-cxf-cdi
- bin/jaxrs-spec-petstore-server-interface.sh to update samples/server/petstore/jaxrs-spec-interface
- bin/jaxrs-spec-petstore-server.sh to update samples/server/petstore/jaxrs-spec
add the changes as new commit in this PR (we will squash all small commit of the PR as one single commit when we merge it)

See also: https://github.com/OpenAPITools/openapi-generator/wiki/Pull-Request-Checklist#shippable-ensure-up-to-date

… filter_swagger_annotations

michbeck100 · 2018-08-15T05:46:18Z

I just ran bin/jaxrs-spec-petstore-server.sh, my fault. How can one know which scripts to run?

jmini · 2018-08-15T05:53:24Z

I once generated this table: https://github.com/OpenAPITools/openapi-generator/wiki/Samples-folder#scripts (might be outdated)

I have computed the list for your by looking at the Shippable error report.

If you have time (takes some minutes), you can also run bin/utils/ensure-up-to-date locally.

michbeck100 · 2018-08-15T08:03:58Z

I had to fix some missing imports in efe7014. BTW: it seems that before 82eba8d this wan't working at all. And i don't really know what this is good for.

jmini · 2018-08-15T16:05:56Z

Thank you a lot for this contribution

wing328 · 2018-08-22T13:10:21Z

@michbeck100 thanks for the enhancement, which is included in the v3.2.2 stable release: https://twitter.com/oas_generator/status/1032252335131512832

Michael Kottenand others added 8 commits August 13, 2018 15:44

Use parameter "useSwaggerAnnotations" to disable swagger annotations …
aed302d
…in generated code. By default annotations are generated.

Remove import for ApiModel at fromModel(..), postProcessModelProperty…
82eba8d
…(..) is too early

Merge branch 'master' into filter_swagger_annotations
4ffccae
# Conflicts: # modules/openapi-generator/src/main/java/org/openapitools/codegen/languages/JavaJAXRSSpecServerCodegen.java

Remove swagger annotations only if useSwaggerAnnotations is false
26902cf

Merge branch 'master' into filter_swagger_annotations
10cf7f7

update Petstore sample so that CIs can verify the change
f8dae32

Prepare version 3.2.2-SNAPSHOT (#810)
e45c53c

Merge branch 'master' into filter_swagger_annotations
e9916c7

michbeck100 changed the title ~~Filter swagger annotations~~[JAXRS-spec] Filter swagger annotations for OpenAPI compatibilityAug 14, 2018

jmini mentioned this pull request Aug 14, 2018
[JAXRS-spec] Make path for openapi.yaml configurable #809
Closed

Michael Kotten added 2 commits August 15, 2018 07:43

update Petstore sample so that CIs can verify the change
c8c67e4

Merge remote-tracking branch 'origin/filter_swagger_annotations' into…
203a7c2
… filter_swagger_annotations

Removed microprofile openapi dependency for now
145fc68

michbeck100 mentioned this pull request Aug 15, 2018
[JAXRS-spec] Use Microprofile Openapi annotations instead of swagger #795
Open

Michael Kotten added 3 commits August 15, 2018 08:22

update Petstore sample so that CIs can verify the change
daaa63d

Just remove jackson imports if jackson is not used
efe7014

update Petstore sample so that CIs can verify the change
8c33497

jmini merged commit fa52826 into OpenAPITools:masterAug 15, 2018

jmini added the Server: Java label Aug 15, 2018

jmini added this to the 3.2.2 milestone Aug 15, 2018

jmini changed the title ~~[JAXRS-spec] Filter swagger annotations for OpenAPI compatibility~~[JAXRS-spec] Add option useSwaggerAnnotations (for MicroProfile-OpenAPI)Aug 15, 2018

michbeck100 deleted the filter_swagger_annotations branch August 16, 2018 06:28

jmini mentioned this pull request Aug 21, 2018
[Java-server] Fix improper quoting of default values for query parameters #708
Merged
4 tasks

A-Joshi pushed a commit to ihsmarkitoss/openapi-generator that referenced this pull request Feb 27, 2019
[JAXRS-spec] Add option useSwaggerAnnotations (OpenAPITools#813)
3306f45

jmini mentioned this pull request Oct 1, 2019
[jaxrs-spec] add Eclipse MicroProfile file based approach #3901
Merged