You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Michael Vorburger (Jira)" <ji...@apache.org> on 2020/10/09 18:08:00 UTC
[jira] [Commented] (FINERACT-1189) fineract-client as separate
module
[ https://issues.apache.org/jira/browse/FINERACT-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17211247#comment-17211247 ]
Michael Vorburger commented on FINERACT-1189:
---------------------------------------------
[~Grandolf49] this issue may interest you to watch, re. FINERACT-1102?
> 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)