[REQ] current kotlin-spring generator is using old versions.

[thawkins]

Description

Kotlin-spring template should be updated to use

spring-boot 2.2.--RELEASE currently using 2.2.0-M3
kotlin version 1.3.50 currently using 1.3.30

openapi-generator version

4.1.3

[wing328]

@thawkins I wonder if you can help file a PR to update the dependency version when you've time. I can show you some good starting points to start with.

[thawkins]

Yes, I don't mind doing that, i have forked the repo I will hunt down the templates... Just an observation, is there not perhaps a case of having a central dictionary of component versions that can be included as references into the mustache templates, so that these old versions don't end up being fossilized in them. something like def_springboot_version="2.2.0.RELEASE" def_kotlin_version="1.3.50" it would also enable a CLI switch the opportunity to change them. Obviously there are cases where particular versions need to be maintained because of inter component dependencies, but there are many cases where that is not an issue and having a default may make things easy to maintain.

…

On Wed, Nov 6, 2019 at 12:13 PM William Cheng ***@***.***> wrote: @thawkins <https://github.com/thawkins> I wonder if you can help file a PR to update the dependency version when you've time. I can show you some good starting points to start with. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4369?email_source=notifications&email_token=AAADRSJJ7B44XTZXKOANPG3QSI77ZA5CNFSM4JI5UOX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDFGLCQ#issuecomment-550135178>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAADRSOTU63WW6C3ENAF2J3QSI77ZANCNFSM4JI5UOXQ> .

[wing328]

The Kotlin spring templates can be found in https://github.com/OpenAPITools/openapi-generator/tree/master/modules/openapi-generator/src/main/resources/kotlin-spring

[wing328]

Just an observation, is there not perhaps a case of having a central dictionary of component versions that can be included as references into the mustache templates, so that these old versions don't end up being fossilized in them. something like

Thanks for the suggestion. That's definitely one way to do it. Currently, our approach is to keep the setting within the generator itself. If it's a global setting, likely one single change will require many efforts to ensure the version update won't break other generators (e.g. there are many Java generators that we need to verify.