[
https://issues.apache.org/jira/browse/FINERACT-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215890#comment-17215890
]
Chinmay Kulkarni commented on FINERACT-1189:
--------------------------------------------
[~vorburger] Yes, Open API Generator is the official one (I actually had a
quick chat with William Cheng about this). Swagger Codegen will be supported
and is as active as OpenAPI Generator.
We used org.hidetake.swagger.generator because Swagger Codegen only has a Maven
plugin and not a gradle plugin. You can check here:
[https://github.com/swagger-api/swagger-codegen/tree/master/modules].
When I was exploring on how to shift to Open API Generator, I faced some issues
with it and hidetake was working fine. So I didn't explore that much.
> fineract-client as separate module
> ----------------------------------
>
> Key: FINERACT-1189
> URL: https://issues.apache.org/jira/browse/FINERACT-1189
> Project: Apache Fineract
> Issue Type: Sub-task
> Reporter: Michael Vorburger
> Assignee: Aleksandar Vidakovic
> Priority: Major
>
> Would it be possible to extract JUST the work related to making
> fineract-client as separate module from
> [https://github.com/apache/fineract/compare/develop...vidakovic:feature/FINERACT-1171]?
> In terms of logical sequencing, perhaps this would be simplest to do after
> FINERACT-1188, with fineract-client as the 1st of more to come modules, but
> not yet including fineract-api and fineract-doc?
> I imagine that this would help with later making FINERACT-1102 possible?
> If it's possible, it's perhaps easier if you do not yet include any
> improvements to fineract-client - JUST the build changes, and then raise a
> separate PR after for changes such as adding
> src/main/templates/java/retrofit2/CollectionFormats.mustache and all those
> things? Create a separate JIRA, as a subtask here or standalone Improvement,
> about whatever all those changes are required for.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
