Re: Issues regarding the Fineract client

[Michael Vorburger]

Hi again Ishan,

Thanks for reverting back to me. But please, do not remove the CC line, and
keep your colleagues and the previously added Fineract dev list; so that
others may chime in (and find this through search) - communication on and
participation in an open mailing list instead of private 1:1 DM emails are
one of the fundamental tenets of actively participating in an open source
community, which I'm sure is what you are interested in.

On Mon, May 15, 2023 at 8:06 AM Ishan Ranasingh  wrote:

> Hello Michael,
> Thank you for getting back to me.
> In response to your question, this I the repo I'm referring to:
> https://github.com/openMF/fineract-client
> This above repo out of sync with the main repo(develop branch):
> https://github.com/apache/fineract
> Thanking you,
> Ishan Ranasingh
>

As per the https://github.com/openMF/fineract-client/blob/master/README.md :

*This library duplicates & overlaps with the "official" Apache Fineract
client library
<https://github.com/apache/fineract/blob/develop/fineract-doc/src/docs/en/chapters/sdk/client.adoc>,
see #29 <https://github.com/openMF/fineract-client/issues/29>.*

Could I encourage you to switch from using openMF/fineract-client to
apache/fineract's SDK client lib?

BTW I have fixed a few related links yesterday, just FYI:

*
https://github.com/openMF/fineract-client/commit/14e5c0a2406082e8ac5d5e8e443bd45a64d91f93

* https://github.com/apache/fineract/pull/3175

* https://github.com/apache/fineract/pull/3174

I hope this helps you to pursue what you are?

Best,
M.
___
Michael Vorburger
http://www.vorburger.ch


> On Sun, May 14, 2023 at 7:33 PM Michael Vorburger 
> wrote:
>
>> Hallo Ishan,
>>
>> I unfortunately have been very busy professionally (at work) and not had
>> much time lately to be involved in Fineract. I hope that you do not mind
>> that I copy the Fineract dev list (which I am still subscribed to, but
>> lately haven't been able to read along every message anymore) to our
>> exchange here, so that others may chime in? +dev@fineract.apache.org
>>
>> When you say "fineract client" here, which one do you mean - which GitHub
>> repo? As far as I remember, last time I checked, there unfortunately used
>> to be at least 2 of them... the "new" one in the Fineract main repo, which
>> I had contributed to at some point, and an older standalone one somewhere.
>> That older one could (I can't remember where it was, is that's the one you
>> mean?) may well have fallen out of sync with recent changes to the Fineract
>> REST API. The newer one inside the Fineract main repo should be
>> "auto-updating" during builds - as far as I remember.
>>
>> Please do let me know if this answers your question, or we we (community,
>> more than myself personally) can help with anything else about this.
>>
>> Tx,
>> M.
>> ___
>> Michael Vorburger
>> http://www.vorburger.ch
>>
>>
>> On Sun, May 14, 2023 at 1:04 PM Ishan Ranasingh 
>> wrote:
>>
>>> Hello Mike,
>>> This email is about the fineract client. Is the active development of it
>>> is stopped as I could not find some of the necessary fields in sync with
>>> the fineract: https://github.com/apache/fineract
>>> Thanking you,
>>> Ishan Ranasingh
>>>
>>>

Re: Help on https://github.com/openMF/fineract-client topic

[Michael Vorburger]

Hello Madjey,

I unfortunately have been very busy professionally (at work) and not had
much time lately to volunteer for maintaining Fineract. I hope that you do
not mind that I copy the Fineract dev list (which I am still subscribed to,
but lately haven't been able to read along every message anymore) to our
exchange here, so that others may chime in? +dev@fineract.apache.org

On Sun, May 14, 2023, 16:32 Madjey Mensah  wrote:

> Hi mike,
>
> How are you ?
> I'm trying to execute the main class but I get an error on subscribeOn
> method.
> subscribeOn is not recognize. I think it is a possible problem of
> library incompatibility.
> In the example you use reactivex library but the FineractClient use rx.
> library.
>
> Please, can you help me.
>
> Thank you in advance.
>
> Best regards
>

As per the https://github.com/openMF/fineract-client/blob/master/README.md :

*This library duplicates & overlaps with the "official" Apache Fineract
client library
,
see #29 .*

Could I encourage you to switch from openMF/fineract-client to
apache/fineract's SDK client lib?

BTW I have fixed a few related links, just FYI:

*
https://github.com/openMF/fineract-client/commit/14e5c0a2406082e8ac5d5e8e443bd45a64d91f93

* https://github.com/apache/fineract/pull/3175

* https://github.com/apache/fineract/pull/3174

I hope this helps.

Best,
M.

>

Re: Issues regarding the Fineract client

[Michael Vorburger]

Hallo Ishan,

I unfortunately have been very busy professionally (at work) and not had
much time lately to be involved in Fineract. I hope that you do not mind
that I copy the Fineract dev list (which I am still subscribed to, but
lately haven't been able to read along every message anymore) to our
exchange here, so that others may chime in? +dev@fineract.apache.org

When you say "fineract client" here, which one do you mean - which GitHub
repo? As far as I remember, last time I checked, there unfortunately used
to be at least 2 of them... the "new" one in the Fineract main repo, which
I had contributed to at some point, and an older standalone one somewhere.
That older one could (I can't remember where it was, is that's the one you
mean?) may well have fallen out of sync with recent changes to the Fineract
REST API. The newer one inside the Fineract main repo should be
"auto-updating" during builds - as far as I remember.

Please do let me know if this answers your question, or we we (community,
more than myself personally) can help with anything else about this.

Tx,
M.
___
Michael Vorburger
http://www.vorburger.ch


On Sun, May 14, 2023 at 1:04 PM Ishan Ranasingh  wrote:

> Hello Mike,
> This email is about the fineract client. Is the active development of it
> is stopped as I could not find some of the necessary fields in sync with
> the fineract: https://github.com/apache/fineract
> Thanking you,
> Ishan Ranasingh
>
>

Refusing to allow a GitHub App to create or update workflow without `workflows` permission

[Michael Vorburger]

Hello,

Long time no see, sorry I have been busy.

Today I tried to git push to my fork from a GitHub Codespace (for the first
time), and hit this error:

$ git push vorburger-https
Enumerating objects: 51, done.
Counting objects: 100% (51/51), done.
Delta compression using up to 4 threads
Compressing objects: 100% (30/30), done.
Writing objects: 100% (39/39), 3.04 KiB | 778.00 KiB/s, done.
Total 39 (delta 21), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (21/21), completed with 7 local objects.
To https://github.com/vorburger/fineract.git
 ! [remote rejected] temi-ro_FINERACT-1224_NullPointerException-rebased
-> temi-ro_FINERACT-1224_NullPointerException-rebased (refusing to allow a
GitHub App to create or update workflow
`.github/workflows/build-docker-mariadb.yml` without `workflows` permission)
error: failed to push some refs to '
https://github.com/vorburger/fineract.git'

Has anyone run into this before and has any idea what this "Refusing to
allow a GitHub App to create or update workflow without `workflows`
permission" means?

Tx,
M.
_______
Michael Vorburger
http://www.vorburger.ch

Re: [NOTICE] Introducing GitHub Actions build status notification for git repositories.

[Michael Vorburger]

I would NOT enable this, because getting emails on this mailing list for
each failed build using GitHub Actions, or a change from failure in
previous builds to a successful build, is probably too "noisy" here.


On Sat, Mar 26, 2022 at 11:54 PM Awasum Yannick  wrote:

>
>
> -- Forwarded message -
> From: Daniel Gruno 
> Date: Sat, Mar 26, 2022, 21:58
> Subject: [NOTICE] Introducing GitHub Actions build status notification for
> git repositories.
> To: 
>
>
> Dear Apache projects,
> We are happy to announce yet another feature in our beloved .asf.yaml
> file, namely GitHub Actions build status emails. As the name suggests,
> these are emails that notify of either a failed build using GitHub
> Actions, or a change from failure in previous builds to a successful
> build. Continuously successful builds will not trigger emails, as that
> could be rather spammy.
>
> If your project uses GitHub Actions and wishes to enable status
> notification emails, please see our documentation on this at:
> https://s.apache.org/asfyaml-gha
>
> In short, what you need to do is add a 'jobs' directive to your existing
> notifications section in .asf.yaml if you have such a file (or create it
> if you want this feature), for example:
>
> notifications:
>jobs:  d...@foobar.apache.org
>
> We hope this feature will help our projects, and look forward to any
> feedback you may have, at: us...@infra.apache.org
>
> With regards,
> Daniel on behalf of the ASF Infra Team.
>
>
> PS: Do note that this does not apply to subversion mirrors on GitHub,
> as .asf.yaml is not enabled for these repositories.
>
>

Re: [ANNOUNCE] Apache Fineract 1.6.0 Release

[Michael Vorburger]

Whoot whoot! Congratulations to everyone, well done.

I have just tweeted it as
https://twitter.com/ApacheFineract/status/1500139656704319491, please ❤️ &
RT!

On Thu, Feb 24, 2022 at 8:46 PM VICTOR MANUEL ROMERO RODRIGUEZ <
victor.rom...@fintecheando.mx> wrote:

> Hello Fineract Community,
>
> Congratulations! A great job!
>
> Regards
>
> Victor Romero
>
> El jue, 24 feb 2022 a las 7:36, Aleksandar Vidakovic ()
> escribió:
>
>> The Apache Fineract project is pleased to announce the release of Apache
>> Fineract 1.6.0. The release is available for download from
>> https://fineract.apache.org/#downloads
>>
>> Fineract provides a reliable, robust, and affordable solution for
>> entrepreneurs, financial institutions, and service providers to offer
>> financial services to the world’s 2 billion underbanked and unbanked.
>> Fineract is aimed at innovative mobile and cloud-based solutions, and
>> enables digital transaction accounts for all.
>>
>> This release addressed 99 issues.
>>
>> Readme: https://github.com/apache/fineract/blob/1.6.0/README.md
>>
>> Release page:
>> https://cwiki.apache.org/confluence/display/FINERACT/1.6.0+-+Apache+Fineract
>>
>> List of fixed issues:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12349949=Html=12319420
>>
>> For more information on Apache Fineract please visit project home page:
>> https://fineract.apache.org
>>
>> The Apache Fineract Team
>>
>

Habemus Dependabot!

[Michael Vorburger]

Hello everyone,

I have been able to (re-)enable automated version upgrade bump PRs
<https://github.com/apache/fineract/pulls?q=is%3Apr+label%3Adependencies+>
for our dependencies!

.github/dependabot.yml
<https://github.com/apache/fineract/blob/develop/.github/dependabot.yml> is
where this is configured, using (now GitHub's) Dependabot. It covers not
just Gradle deps for Java JAR libraries, but also GitHub action versions
<https://github.com/apache/fineract/pulls?q=is%3Apr+is%3Aopen+label%3Agithub_actions>
.

We used to have another tool
<https://github.com/apache/fineract/pulls?q=label%3Arenovate+> which did
something similar like this (the Renovate Bot), but it stopped working last
November; I'm looking into if we could have both or will remove Renovate
<https://github.com/apache/fineract/pull/2075>. Because it's been a while,
there are now many dependencies to upgrade. Doing this now after the 1.6.0
release is great timing, as there will be time to iron out any possible
hiccups until the next release. FYI there is a "rate limiting" and more
such PRs will be opened in the coming days & weeks, as the initial batch is
being reviewed and merged.

https://issues.apache.org/jira/browse/FINERACT-1453 has the full background.

Best,
M.
___
Michael Vorburger
http://www.vorburger.ch

Fwd: [jira] Subscription: Fineract Blockers

[Michael Vorburger]

Here are 20 open Blocker issues from JIRA that anyone interested in moving
Apache Fineract forward would be very welcome to contribute to!

PS: Further analyzing and "triaging" any such issues, e.g. by closing
anything that's not relevant anymore, or adding further analysis even if
not fixing yet, is a great form of contribution as well, of course.

_______
Michael Vorburger
http://www.vorburger.ch


-- Forwarded message -
From: 
Date: Fri, Mar 4, 2022 at 2:00 AM
Subject: [jira] Subscription: Fineract Blockers
To: 




Issue Subscription
Filter: Fineract Blockers
<https://issues.apache.org/jira/issues/?filter=12349014> (20 issues)
Subscriber: vorburger
T Patch Info Key Summary Assignee Reporter P Status Resolution Created Updated
Due Development
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1121>
FINERACT-1121 <https://issues.apache.org/jira/browse/FINERACT-1121>

NoSuchElementException at
AbstractLoanScheduleGenerator.checkIfFirstRepaymentDateisOnHolidayOrNonWorkingDay
<https://issues.apache.org/jira/browse/FINERACT-1121>
*Unassigned* Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Open *Unresolved* 20/Aug/20 20/Aug/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1248>
FINERACT-1248 <https://issues.apache.org/jira/browse/FINERACT-1248>

RecurringDepositTest >
testRecurringDepositAccountWithClosureTypeTransferToSavings_WITH_HOLD_TAX:
Journal Entry not found ==> expected:  but was: https://issues.apache.org/jira/browse/FINERACT-1248>
*Unassigned* Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Open *Unresolved* 31/Oct/20 31/Oct/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1254>
FINERACT-1254 <https://issues.apache.org/jira/browse/FINERACT-1254>

There is no option to create quarterly principal and monthly Interest
repayment method... <https://issues.apache.org/jira/browse/FINERACT-1254>
*Unassigned* Mukundhan
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Mkd-d> [image:
Blocker] Open *Unresolved* 06/Nov/20 10/Nov/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1260>
FINERACT-1260 <https://issues.apache.org/jira/browse/FINERACT-1260>

EntityExistsException: Cannot delete or update a parent row: a foreign key
constraint fails
(`fineract_default`.`m_loan_transaction_repayment_schedule_mapping`,
CONSTRAINT `FK_mappings_m_loan_repayment_schedule`...
<https://issues.apache.org/jira/browse/FINERACT-1260>
*Unassigned* Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Open *Unresolved* 12/Nov/20 26/Nov/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1122>
FINERACT-1122 <https://issues.apache.org/jira/browse/FINERACT-1122>

NullPointerException at DepositAccountInterestRateChartData.from()
<https://issues.apache.org/jira/browse/FINERACT-1122>
*Unassigned* Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Open *Unresolved* 20/Aug/20 04/Jan/21
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1086>
FINERACT-1086 <https://issues.apache.org/jira/browse/FINERACT-1086>

JpaOptimisticLockingFailureException at
LoanSchedularServiceImpl.recalculateInterest() - requires retry logic?
<https://issues.apache.org/jira/browse/FINERACT-1086>
*Unassigned* Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Open *Unresolved* 11/Jul/20 15/Jan/21
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1326>
FINERACT-1326 <https://issues.apache.org/jira/browse/FINERACT-1326>

Migration V327_1__creditbureau_integration.sql failed
<https://issues.apache.org/jira/browse/FINERACT-1326>
*Unassigned* Anu Omotayo
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=anmotayo> [image:
Blocker] Open *Unresolved* 09/Mar/21 05/Apr/21
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1267>
FINERACT-1267 <https://issues.apache.org/jira/browse/FINERACT-1267>

NullPointerException at ChronoLocalDate.isEqual()
<https://issues.apache.org/jira/browse/FINERACT-1267>
*Unassigned* Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Open *Unresolved* 28/Nov/20 12/Apr/21
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1474>
FINERACT-1474 <https://issues.apache.org/jira/browse/FINERACT-1474>

Remove hard-coded constant from ThitsaworksCreditBureauTest
<https://issues.apache.org/jira/browse/FINERACT-1474>
*Unassigned* Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blo

Fwd: [jira] Subscription: Fineract Resolved Last 3 Weeks

[Michael Vorburger]

Hello everyone,

Below is the customary list of issues resolved in the last 3 weeks (some
still went into 1.6.0, and the others mark the start of 1.7.0).

@Aleks, Arnold, Manoj, Rahul, John and Sandeep: Many thanks for your
contributions! Keep it coming... ;-)

Best,
M.
___
Michael Vorburger
http://www.vorburger.ch


-- Forwarded message -
From: 
Date: Fri, Mar 4, 2022 at 2:00 AM
Subject: [jira] Subscription: Fineract Resolved Last 3 Weeks
To: 




Issue Subscription
Filter: Fineract Resolved Last 3 Weeks
<https://issues.apache.org/jira/issues/?filter=12349983> (15 issues)
Subscriber: vorburger
T Patch Info Key Summary Assignee Reporter P Status Resolution Created Updated
Due Development
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1509>
FINERACT-1509 <https://issues.apache.org/jira/browse/FINERACT-1509>

Gradle wrapper missing in source distribution
<https://issues.apache.org/jira/browse/FINERACT-1509>
Aleksandar Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> Aleksandar
Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> [image:
Minor] Resolved Fixed 21/Feb/22 21/Feb/22
[image: Task] <https://issues.apache.org/jira/browse/FINERACT-1446>
FINERACT-1446 <https://issues.apache.org/jira/browse/FINERACT-1446>

Build performance improvements
<https://issues.apache.org/jira/browse/FINERACT-1446>
Aleksandar Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> Aleksandar
Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> [image:
Major] Resolved Fixed 28/Nov/21 21/Feb/22
[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-1507>
FINERACT-1507 <https://issues.apache.org/jira/browse/FINERACT-1507>

Last minor dependency updates before release
<https://issues.apache.org/jira/browse/FINERACT-1507>
Aleksandar Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> Aleksandar
Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> [image:
Minor] Resolved Fixed 19/Feb/22 19/Feb/22
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1506>
FINERACT-1506 <https://issues.apache.org/jira/browse/FINERACT-1506>

Add WAR artifact to release distribution again
<https://issues.apache.org/jira/browse/FINERACT-1506>
Aleksandar Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> Aleksandar
Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> [image:
Minor] Resolved Fixed 19/Feb/22 19/Feb/22
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1512>
FINERACT-1512 <https://issues.apache.org/jira/browse/FINERACT-1512>

Fix SSL configuration to avoid endless loops behind load balancers
<https://issues.apache.org/jira/browse/FINERACT-1512>
Arnold Galovics
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=arnoldgalovics>
Aleksandar
Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> [image:
Minor] Resolved Fixed 25/Feb/22 25/Feb/22
[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-1498>
FINERACT-1498 <https://issues.apache.org/jira/browse/FINERACT-1498>

Liquibase support <https://issues.apache.org/jira/browse/FINERACT-1498>
Arnold Galovics
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=arnoldgalovics>
Arnold
Galovics
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=arnoldgalovics>
[image:
Major] Resolved Fixed 08/Feb/22 24/Feb/22
[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-1496>
FINERACT-1496 <https://issues.apache.org/jira/browse/FINERACT-1496>

Improve performance for loading a Loan
<https://issues.apache.org/jira/browse/FINERACT-1496>
Arnold Galovics
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=arnoldgalovics>
Arnold
Galovics
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=arnoldgalovics>
[image:
Major] Resolved Fixed 04/Feb/22 23/Feb/22
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1497>
FINERACT-1497 <https://issues.apache.org/jira/browse/FINERACT-1497>

Unable to generate Swagger API on Windows
<https://issues.apache.org/jira/browse/FINERACT-1497>
Arnold Galovics
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=arnoldgalovics>
Arnold
Galovics
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=arnoldgalovics>
[image:
Major] Resolved Fixed 04/Feb/22 20/Feb/22
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1443>
FINERACT-1443 <https://issues.apache.org/jira/browse/FINERACT-1443>

Reschedule loan causing wrong interest calculation of last 3-4 installments
<https://issues.apache.org/jira/browse/FINERACT-1443>

Re: Questions regarding Production-Readiness of Fineract Client

[Michael Vorburger]

gt;
>> Chinmay and Danish,
>>
>> There is some interest and inquiry coming from users in the
>> community regarding the Fineract Client.
>>
>> I was hoping you all along with some of the past contributors to this
>> project like @Aleksandar Vidakovic  and @Michael
>> Vorburger  could help me with some of the
>> below questions:
>>
>> 3. What is the difference between these 2 clients:
>> https://github.com/openMF/fineract/tree/develop/fineract-client
>> https://github.com/openMF/fineract-client
>>
>> Are either of these client’s considered production ready?
>>
>> 4. Is
>> https://github.com/openMF/fineract-client/blob/master/swagger-api-spec-file.json
>>  hand
>> coded or generated?
>>
>> 5. We have noticed that both fineract-clients only have fullname field
>> supported when creating a Fineract Client (the database entity). This has
>> led to the conclusion that neither are based off the Fineract-provider
>> JAX-RS but are probably hand coded. We are wondering which one is best
>> supported now and into the future, or if we should hand code our own client.
>>
>> 6. Have either client been used in high volume use cases?
>>
>>

Re: Mifos Mobile not working

[Michael Vorburger]

Sifiso,

Can you remind us exactly which "self-service mifos mobile app" this is
about - what's the GitHub repo again?

I'm also confused how this relates to "running the latest community app"...
that shouldn't have anything to do with it - unless I'm misunderstanding
what you're saying?

What version of Apache Fineract (not Mifos X, right?) are you trying to
connect to? What goes the server side error log show when whatever mobile
App this is about connects to the API?

Best,
M.


On Mon, 10 Jan 2022, 10:52 ,  wrote:

> Hi Guys,
>
> Has there been a solution for the self-service mifos mobile app. Has
> anyone got it running yet? The latest dev for mifos mobile is still not
> logging in even while running the latest community app.
>
>
>
> The resulting error has not changed after the last merge for issue
> Fineract 726#
>
> D/OkHttp: {"timestamp":1641671332070,"status":400,"error":"Bad
> Request","message":"","path":"/fineract-provider/api/v1/self/authentication"}
>
>
>
> Any assistance on this matter would be appreciated.
>
>
>
> Kind regards,
>
> Sifiso
>

Re: Broken Link

[Michael Vorburger]

Hello Kigred,

Sorry for a (very) late reply here (I'm doing a "bulk catch up" on several
months of email traffic LOL), but in case you are still interested,
just wanted to let you know that the demo server of the Apache Fineract
community project is https://www.fineract.dev now; https://demo.openmf.org
has been shut down.

Re. Architecture documentation and such, perhaps
https://github.com/apache/fineract/tree/develop/fineract-doc/src/docs/en is
of interest to you? We welcome any contributions you may wish to make to
those docs, BTW!

Best,
M.
_______
Michael Vorburger
http://www.vorburger.ch


On Sun, Sep 12, 2021 at 10:10 PM Kigred Developer <
kigred.develo...@gmail.com> wrote:

> The link to the software architecture documentation is broken.
> https://demo.openmf.org/architecture/
>

Re: Fineract project in SonarCloud

[Michael Vorburger]

Yeah it was Victor, see https://github.com/apache/fineract/pull/1893.

BTW perhaps someone reading along here would be up for taking on
https://issues.apache.org/jira/browse/FINERACT-1483 ?


On Fri, Jan 7, 2022 at 12:35 PM Michael Vorburger  wrote:

> +Victor Romero  if I'm not mistaken, you
> had set up Sonar Cloud?
>
>
> On Thu, 6 Jan 2022, 00:01 Petri Tuomola,  wrote:
>
>> Hi all
>>
>> Who has the admin rights to the fineract project in SonarCloud? I’d like
>> to migrate this to use Github Actions so that we can decommission the
>> Travis build script altogether, but for this I’d need admin rights to
>> generate a new project key. I have access to SonarCloud but not to the
>> fineract project.
>>
>> Not sure who set this up originally - but if anyone has any idea on how
>> to get added as admin, it would be great to hear from you…
>>
>> Regards
>> Petri
>>
>>

Fwd: [jira] Subscription: Fineract Blockers

[Michael Vorburger]

And here are 18 open Blocker issues from JIRA that anyone interesting in
moving this wonderful project forward would be very welcome to contribute
to:

PS: Further analyzing and "triaging" any such issues is a form of
contribution as well, of course¨


-- Forwarded message -
From: 
Date: Fri, Jan 7, 2022 at 2:00 AM
Subject: [jira] Subscription: Fineract Blockers
To: 




Issue Subscription
Filter: Fineract Blockers
<https://issues.apache.org/jira/issues/?filter=12349014> (18 issues)
Subscriber: vorburger
T Patch Info Key Summary Assignee Reporter P Status Resolution Created Updated
Due Development
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1121>
FINERACT-1121 <https://issues.apache.org/jira/browse/FINERACT-1121>

NoSuchElementException at
AbstractLoanScheduleGenerator.checkIfFirstRepaymentDateisOnHolidayOrNonWorkingDay
<https://issues.apache.org/jira/browse/FINERACT-1121>
*Unassigned* Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Open *Unresolved* 20/Aug/20 20/Aug/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1248>
FINERACT-1248 <https://issues.apache.org/jira/browse/FINERACT-1248>

RecurringDepositTest >
testRecurringDepositAccountWithClosureTypeTransferToSavings_WITH_HOLD_TAX:
Journal Entry not found ==> expected:  but was: https://issues.apache.org/jira/browse/FINERACT-1248>
*Unassigned* Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Open *Unresolved* 31/Oct/20 31/Oct/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1254>
FINERACT-1254 <https://issues.apache.org/jira/browse/FINERACT-1254>

There is no option to create quarterly principal and monthly Interest
repayment method... <https://issues.apache.org/jira/browse/FINERACT-1254>
*Unassigned* Mukundhan
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Mkd-d> [image:
Blocker] Open *Unresolved* 06/Nov/20 10/Nov/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1260>
FINERACT-1260 <https://issues.apache.org/jira/browse/FINERACT-1260>

EntityExistsException: Cannot delete or update a parent row: a foreign key
constraint fails
(`fineract_default`.`m_loan_transaction_repayment_schedule_mapping`,
CONSTRAINT `FK_mappings_m_loan_repayment_schedule`...
<https://issues.apache.org/jira/browse/FINERACT-1260>
*Unassigned* Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Open *Unresolved* 12/Nov/20 26/Nov/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1266>
FINERACT-1266 <https://issues.apache.org/jira/browse/FINERACT-1266>

NullPointerException at SavingsHelper.determineInterestPostingPeriods()
<https://issues.apache.org/jira/browse/FINERACT-1266>
*Unassigned* Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Open *Unresolved* 28/Nov/20 28/Nov/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1122>
FINERACT-1122 <https://issues.apache.org/jira/browse/FINERACT-1122>

NullPointerException at DepositAccountInterestRateChartData.from()
<https://issues.apache.org/jira/browse/FINERACT-1122>
*Unassigned* Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Open *Unresolved* 20/Aug/20 04/Jan/21
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1086>
FINERACT-1086 <https://issues.apache.org/jira/browse/FINERACT-1086>

JpaOptimisticLockingFailureException at
LoanSchedularServiceImpl.recalculateInterest() - requires retry logic?
<https://issues.apache.org/jira/browse/FINERACT-1086>
*Unassigned* Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Open *Unresolved* 11/Jul/20 15/Jan/21
[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-1168>
FINERACT-1168 <https://issues.apache.org/jira/browse/FINERACT-1168>

Integration Tests failure due to internal server errors should show server
side failure stack trace
<https://issues.apache.org/jira/browse/FINERACT-1168>
*Unassigned* Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Open *Unresolved* 30/Sep/20 07/Feb/21
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1326>
FINERACT-1326 <https://issues.apache.org/jira/browse/FINERACT-1326>

Migration V327_1__creditbureau_integration.sql failed
<https://issues.apache.org/jira/browse/FINERACT-1326>
*Unassigned* Anu Omotayo
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=anmotayo> [image:
Blocker] Open *Unresolved* 09/Mar/21 05/Apr/21
[image: Bug] <https://issues.apache.org

Re: Recent improvemnts...

[Michael Vorburger]

This is incredible work!! Amazing contributions, Aleks.

PS: FYI https://github.com/vorburger/www.fineract.dev/issues/11 re. related
https://www.fineract.dev impact (will eventually fix it).


On Tue, 4 Jan 2022, 06:11 Aleksandar Vidakovic, 
wrote:

> Hi everyone,
>
> ... just wanted to give you a bit of an update on some recent improvements
> that have an impact on build speed and development experience:
>
>
> *OpenJPA plugin*
>
> Petri spent some time getting the OpenJPA plugin to do the enhancement
> processing in a way to take full advantage of the build cache. This one is
> actually a major speed improvement overall as it allows now for truly
> incremental compilation of "fineract-provider" (you'll see, the first
> compile takes quite some time... there's a lot of code, but the second one
> just skips when no changes to the sources were made.
>
>
> *Fix Gradle compiler parameters*
>
> This was an odd one. Turns out if you add compiler parameters multiple
> times then this slows down the build process significantly (I have no
> explanation, just experimentation). That one is on me, I introduced this a
> while back, because I didn't see that we can add all parameters at once.
> Low hanging fruit.
>
>
> *Automatic build script version management based on Git tags and Git
> hashes*
>
> This one is a little bit of a convenience. Until now we manually set (or
> not) a property ("releaseVersion") in gradle.properties to determine the
> version of Fineract. This is easy to forget when doing the releases. Now
> that we have Docker builds based on a Gradle plugin this also comes in
> handy when setting the Docker tags (just use the "$version" variable). The
> only thing we need to do now are proper releases with Git tags. Git hashes
> will be part of the version number during development (pull requests,
> develop branch); when we do a release (in master) the version pattern
> automatically follows the Semantic Versioning rules (no Git hash). BTW: Git
> hashes change on every commit; like this all important artifacts become
> uniquely identifiable no matter which branch you are working in.
>
>
> *Create separate sub-project for WAR build*
>
> We have now a separate module for the WAR build. This was done in
> preparation to improve the integration tests, but also to simplify the
> "fineract-provider" build script (was needed for the Docker build
> improvement).
> Note: personally I would drop this deliverable sooner than later; with a
> proper Docker image build in place this shouldn't be needed anymore. We
> used it here mainly for setting up tests (see my comments below concerning
> "Testcontainers"). Is there a significant audience that still uses these
> WAR files in production?
>
>
> *Docker image build with Gradle Jib plugin*
>
> I'm pretty sure up until now the Docker image build via the
> docker-compose.yml file was slowing down pretty much everyone. On my
> machine this took > 10min, because the Dockerfile contained one section
> that did a Gradle build inside a Docker container and the results of that
> build were then used to populate the actual Docker image. Because
> everything ran in a Docker container that build could not take advantage of
> any caches outside of it where we did pretty much the same. So, instead of
> having to build twice we now only have one run that takes advantage of
> Gradle's build cache and the Docker image is built now by Google's Jib
> plugin which is very fast (just a couple of secs) and does some
> optimizations to keep the images small.
>
>
> *Replace Tomcat Cargo plugin to run integration tests with Testcontainers*
>
> This is a major improvement for the development experience. Until now it
> was a bit complicated to run the integration tests locally. You needed a
> separate MySQL instance running that required some initialization (see
> Gradle script "createDb" tasks). This also made it a bit inconvenient to
> run those tests in your IDE. Not anymore! Now that we have a Docker image
> as part of the build process we re-use it immediately for those integration
> tests. The Testcontainers  framework brings Docker to JUnit 5 tests with
> not much effort. Actually, the only changes I applied to the existing tests
> were to make sure that the proper ports are used (Testcontainers uses
> random ports which allows you to run - in theory - multiple Fineract
> instances side by side) and in some cases I needed to enforce a certain
> execution order of test functions, because they had concurrency issues.
> Looks like not all tests are thread safe. Which reminds me that I've
> tentatively enabled parallel test execution to speed up things.
> I also got rid of the separate modules for OAuth2 and 2FA integration
> testing; this can now be done in the same module. Simpler Github Actions
> workflow.
> Note: this PR is still in progress, but looks already promising. More
> changes on the testing front coming (Cucumber, faster JUnit tests with
> minimal or no Docker container 

InaccessibleObjectException - Unable to make field private final byte java.time.LocalTime.hour accessible: module java.base does not "opens java.time" to unnamed module

[Michael Vorburger]

Would someone like to create a JIRA about and someone (else, possibly) be
interested in fixing the problem below, re. an
java.lang.reflect.InaccessibleObjectException - Unable to make field
private final byte java.time.LocalTime.hour accessible: module java.base
does not "opens java.time" to unnamed module at
org.apache.fineract.infrastructure.core.serialization.ExcludeNothingWithPrettyPrintingOffJsonSerializerGoogleGson.serialize?

It happens with our latest code now running on https://www.fineract.dev...
actually running code is always useful to find issues! ;-) It would also be
useful to add a unit and/or an integration test to catch this regression
earlier.

PS: The View Error Details link at the end will work for any active
committers who want access to Fineract.dev's Error Reporting; please
comment on https://github.com/vorburger/www.fineract.dev/issues/9 to get
added, if you are an active committer (or PMC member).


-- Forwarded message -
From: 
Date: Thu, 30 Dec 2021, 10:43
Subject: New error in vorburger-learn-appengin demo 20211229t215907
To: 


[image: Google Cloud Platform]

New error in vorburger-learn-appengin demo 20211229t215907
java.lang.reflect.InaccessibleObjectException
Unable to make field private final byte java.time.LocalTime.hour
accessible: module java.base does not "opens java.time" to unnamed module
@73d4cc9e
java.lang.reflect.InaccessibleObjectException: Unable to make field private
final byte java.time.LocalTime.hour accessible: module java.base does not
"opens java.time" to unnamed module @73d4cc9e at
java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
at
java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:178)
at java.base/java.lang.reflect.Field.setAccessible(Field.java:172) at
com.google.gson.internal.reflect.UnsafeReflectionAccessor.makeAccessible(UnsafeReflectionAccessor.java:44)
at
com.google.gson.internal.bind.ReflectiveTypeAdapterFactory.getBoundFields(ReflectiveTypeAdapterFactory.java:159)
at
com.google.gson.internal.bind.ReflectiveTypeAdapterFactory.create(ReflectiveTypeAdapterFactory.java:102)
at com.google.gson.Gson.getAdapter(Gson.java:489) at
com.google.gson.internal.bind.ReflectiveTypeAdapterFactory.createBoundField(ReflectiveTypeAdapterFactory.java:117)
at
com.google.gson.internal.bind.ReflectiveTypeAdapterFactory.getBoundFields(ReflectiveTypeAdapterFactory.java:166)
at
com.google.gson.internal.bind.ReflectiveTypeAdapterFactory.create(ReflectiveTypeAdapterFactory.java:102)
at com.google.gson.Gson.getAdapter(Gson.java:489) at
com.google.gson.internal.bind.CollectionTypeAdapterFactory.create(CollectionTypeAdapterFactory.java:53)
at com.google.gson.Gson.getAdapter(Gson.java:489) at
com.google.gson.internal.bind.ReflectiveTypeAdapterFactory.createBoundField(ReflectiveTypeAdapterFactory.java:117)
at
com.google.gson.internal.bind.ReflectiveTypeAdapterFactory.getBoundFields(ReflectiveTypeAdapterFactory.java:166)
at
com.google.gson.internal.bind.ReflectiveTypeAdapterFactory.create(ReflectiveTypeAdapterFactory.java:102)
at com.google.gson.Gson.getAdapter(Gson.java:489) at
com.google.gson.internal.bind.CollectionTypeAdapterFactory.create(CollectionTypeAdapterFactory.java:53)
at com.google.gson.Gson.getAdapter(Gson.java:489) at
com.google.gson.internal.bind.ReflectiveTypeAdapterFactory.createBoundField(ReflectiveTypeAdapterFactory.java:117)
at
com.google.gson.internal.bind.ReflectiveTypeAdapterFactory.getBoundFields(ReflectiveTypeAdapterFactory.java:166)
at
com.google.gson.internal.bind.ReflectiveTypeAdapterFactory.create(ReflectiveTypeAdapterFactory.java:102)
at com.google.gson.Gson.getAdapter(Gson.java:489) at
com.google.gson.Gson.toJson(Gson.java:727) at
com.google.gson.Gson.toJson(Gson.java:714) at
com.google.gson.Gson.toJson(Gson.java:669) at
com.google.gson.Gson.toJson(Gson.java:649) at
org.apache.fineract.infrastructure.core.serialization.ExcludeNothingWithPrettyPrintingOffJsonSerializerGoogleGson.serialize(ExcludeNothingWithPrettyPrintingOffJsonSerializerGoogleGson.java:44)
at
org.apache.fineract.infrastructure.core.serialization.DefaultToApiJsonSerializer.serialize(DefaultToApiJsonSerializer.java:57)
at
org.apache.fineract.infrastructure.core.serialization.DefaultToApiJsonSerializer.serializeWithSettings(DefaultToApiJsonSerializer.java:133)
at
org.apache.fineract.infrastructure.core.serialization.DefaultToApiJsonSerializer.serialize(DefaultToApiJsonSerializer.java:83)
at
org.apache.fineract.portfolio.client.api.ClientsApiResource.retrieveTemplate(ClientsApiResource.java:152)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method) at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at

Fineract.dev Demo Server Update

[Michael Vorburger]

Hello everyone,

https://www.fineract.dev has been running on code from
https://github.com/apache/fineract stuck on 2021-09-21 and has failed to
automagically update itself to the very latest and greatest bleeding edge
version of our code, like it used to.  Someone had also changed the mifos
user's password password. (Contact me if you are interested in a separate
tenant for your dedicated use.)

I have spent a couple of hours fixing a number of things related to this
yesterday and today. https://www.fineract.dev now runs the very latest code
again, and it auto-updates with a every merged PR again, as it used to. It
now also prevents password changes. Full technical details available below;
please comment on the respective JIRA issues instead of replying about
those details here on this email thread if you want to chime in about those
particular issues I've encountered.

Happy Holidays, and best wishes for 2022 to all of you.

M.

1. https://github.com/vorburger/www.fineract.dev/issues/8 CD broken

2. https://issues.apache.org/jira/browse/FINERACT-1454 Container should not
assume that DB hostname is fixed hard-coded fineractmysql (and port 3306),
fixed by https://github.com/apache/fineract/pull/2004

3. https://issues.apache.org/jira/browse/FINERACT-1456 Replacement of MySQL
by MariaDB JDBC driver is a regression in the container image

4. https://issues.apache.org/jira/browse/FINERACT-1457 Fineract no longer
works with MySQL 5.7 due to Flyway v8 upgrade

5. https://issues.apache.org/jira/browse/FINERACT-1459 Data Migration issue
(Subquery returns more than 1 row) in
V370__message_gateway_hook_template.sql

6. https://github.com/vorburger/www.fineract.dev/issues/5 mifos account
password changed, fixed permanently using Petri's
https://github.com/apache/fineract/pull/2001 for
https://issues.apache.org/jira/browse/FINERACT-1452 - Thank You, Petri!!

7. https://github.com/vorburger/www.fineract.dev/issues/9 Opening up
Fineract.dev Error Reporting to trusted committers

___
Michael Vorburger
http://www.vorburger.ch

Re: Incubator Release Notes

[Michael Vorburger]

Avik,

On Wed, Dec 29, 2021 at 6:21 PM Avik Ganguly  wrote:

> Hello everyone,
>
>
>>> https://mail-archives.apache.org/mod_mbox/www-announce/201701.mbox/%3CCAOSe2yuhJTNPENs_A3g8OYGM6ymN5tz-kg2NusSwt6=sgpf...@mail.gmail.com%3E
>>
>> The release notes can be found here:
>>
>> https://cwiki.apache.org/confluence/display/FINERACT/0.6.0-incubating+Release-+Apache+Fineract
>
> The above link for incubator fineract release notes is dead. When Fineract
> graduated, did the incubator release notes move to somewhere else or did it
> get removed altogether? Can a Confluence space admin perhaps restore the
> incubator release notes in case they were removed during graduation?
>

I'm probably misunderstand what you are asking, but for me on
https://cwiki.apache.org/confluence/display/FINERACT/0.6.0-incubating+Release-+Apache+Fineract
it currently does still show the following, is this not the incubator
release notes you were hoping to see:

0.6.0-incubating Release- Apache Fineract


   - Created by Nazeer Shaik
   , last
   modified by Myrle Krantz
    on Jan 09, 2017
   



Scope

There are main goals of this release

   - Addressing some of Apache Fineract 0.5.0-incubating review comments
   -

   Share the new feature(s) & bug fixes that have been developed so far, to
   give the community a good sense of the upcoming 0.6.0 release.

Release Artifacts

Download the 0.6.0-incubating release


This release contains both Source & Binary artifacts.
Release Notes

New Features & Improvements

   - Workflow implementation with entity data tables
   - Updating readme.md with relevant user manuals
   - Added instructions in readme.md about how to run RAT

Bugs

   - FINERACT-288 - Client's Image Uploaded Not Showing on UI in Amazon S3
   - FINERACT-260 - Validation need to be added if the client charge is
   applied before client activation date
   - FINERACT-267 - Foreclosure Issue: Loan with Installment fee status is
   overpaid
   - FINERACT-309 - Editing 'Product Mix' Not Working
   -

   FINERACT-361 - Getting
   error.msg.loanschedule.emi.amount.must.be.greter.than.interest on loan
   submit
   -

   Fix to charge fees when total amount changed during approval
   -

   Remove unnecessary checking for missing joined date



With best regards,
> Avik Ganguly.
>
> Disclaimer:
>
> Privileged & confidential information is contained in this message
> (including all attachments). If you are not an intended recipient of this
> message, please destroy this message immediately and kindly notify
> the sender by reply e-mail. Any unauthorised use or dissemination of this
> message in any manner whatsoever, in whole or in part, is strictly
> prohibited. This e-mail, including all attachments hereto, (i) is for
> discussion purposes only and shall not be deemed or construed to be a
> professional opinion unless expressly stated otherwise, and (ii) is not
> intended, written or sent to be used, and cannot and shall not be used, for
> any unlawful purpose. This communication, including any attachments, may
> not be free of viruses, interceptions or interference, and may not be
> compatible with your systems. You should carry out your own virus checks
> before opening any attachment to this e-mail. The sender of this e-mail and
> *Fynarfin Tech Private Limited* shall not be liable for any damage that
> you may sustain as a result of viruses, incompleteness of this message, a
> delay in receipt of this message or computer problems experienced.
>

Re: API documentation link DOWN

[Michael Vorburger]

https://www.fineract.dev points you to
https://demo.fineract.dev/fineract-provider/api-docs/apiLive.htm and
https://demo.fineract.dev/fineract-provider/swagger-ui/index.html

Hope that helps?

On Wed, 22 Dec 2021, 15:42 Luis Espinoza,  wrote:

> Greetings everyone,
>
> The API docs url is down. Is there anyone that can check this out? Or is
> there a specific support mail we should use?
> https://demo.mifos.io/api-docs/apiLive.htm
> 
>
> Best regards.
>
> --
> [image: Logo] 
> *Luis Espinoza* *| Project Manager*
> *e:* luis.espin...@fiter.io
> *w:* fiter.io 
> *m:* +591-72285850
> [image: twitter icon]  [image: youtube icon]
>  [image:
> linkedin icon] 
>

Re: Critical RCE Vulnerability: log4j - CVE-2021-44228

[Michael Vorburger]

Independently confirming this - relax everyone! (As in, you can relax for
Fineract. Don't relax for anything else you are responsible for - do check
any other code you have, this security vulnerability is as bad they can
get; the Internet is rightfully on fire about this.)

https://spring.io/blog/2021/12/10/log4j2-vulnerability-and-spring-boot
(which I found while working on
https://github.com/vorburger/MariaDB4j/issues/509) has some related
background; TL;DR: *"The log4j-to-slf4j and log4j-api jars that we include
in spring-boot-starter-logging cannot be exploited on their own. Only
applications using log4j-core and including user input in log messages are
vulnerable."*

Or, more technically:

$ ./gradlew fineract-provider:dependencies | grep log4j
|||+--- org.apache.logging.log4j:log4j-to-slf4j:2.14.1
||||\--- org.apache.logging.log4j:log4j-api:2.14.1
|||+--- org.apache.logging.log4j:log4j-to-slf4j:2.14.1
||||\--- org.apache.logging.log4j:log4j-api:2.14.1
|||+--- org.apache.logging.log4j:log4j-to-slf4j:2.14.1
||||\--- org.apache.logging.log4j:log4j-api:2.14.1
|||+--- org.apache.logging.log4j:log4j-to-slf4j:2.14.1
||||\--- org.apache.logging.log4j:log4j-api:2.14.1
|||+--- org.apache.logging.log4j:log4j-to-slf4j:2.14.1
||||\--- org.apache.logging.log4j:log4j-api:2.14.1
|||+--- org.apache.logging.log4j:log4j-to-slf4j:2.14.1
||||\--- org.apache.logging.log4j:log4j-api:2.14.1

$ ./gradlew fineract-provider:dependencies | grep log4j-core
(nothing)

Hope this helps everyone to sleep well... ;-)


On Sat, Dec 11, 2021 at 10:28 AM AirsayLongCon 
wrote:

> Hello Aleks
> Thank you for the clarification
>
> On Sat, Dec 11, 2021, 10:17 AM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> Hi,
>>
>> ... we are using SLF4J to abstract all the different logging frameworks
>> (Commons Logging, Log4J etc.). Under the hood logging in Fineract is done
>> by Logback and not Log4j. The only Log4j dependencies we have are those
>> that "redirect" the logging to Logback.
>>
>> Here's also a vulnerability report for that specific dependency
>> ("org.apache.logging.log4j:log4j-to-slf4j"):
>>
>> https://snyk.io/vuln/maven:org.apache.logging.log4j:log4j-to-slf4j
>>
>> FYI
>>
>> Cheers,
>>
>> Aleks
>>
>> On Sat, Dec 11, 2021 at 2:10 AM AirsayLongCon 
>> wrote:
>>
>>> Hello community,
>>> Are we are of the RCE reportedly affecting log4j
>>>
>>> If your organization uses the log4j library, you should upgrade
>>> to log4j-2.1.50.rc2 immediately.
>>>
>>>
>>> https://www.huntress.com/blog/rapid-response-critical-rce-vulnerability-is-affecting-java
>>>
>>

[jira] Subscription: Fineract Resolved Last 6 Weeks

[Michael Vorburger]

Hello everyone,

It's been a while since my last regular such email (on Feb 7th), but below
is the usual list of here 10 issues fixed in Fineract over the last 6 weeks
- we thank Aleks, Benura, David, Manthan, Michael, Petri, Rahul & Zoltán
for their contributions - what a community!!

If YOU want to appear in the next such email, we look forward to your
contributions!

M.
[image: New Feature] <https://issues.apache.org/jira/browse/FINERACT-1177>
FINERACT-1177 <https://issues.apache.org/jira/browse/FINERACT-1177>

Alt. distro? Spring Boot JAR is not great for "dropping in" Plugins
<https://issues.apache.org/jira/browse/FINERACT-1177>
Aleksandar Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks>







[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-1171>
FINERACT-1171 <https://issues.apache.org/jira/browse/FINERACT-1171>

Multi-module configuration for Gradle
<https://issues.apache.org/jira/browse/FINERACT-1171>
Aleksandar Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks>







[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-1324>
FINERACT-1324 <https://issues.apache.org/jira/browse/FINERACT-1324>

Add Kubernetes resource limits to FINERACT server
<https://issues.apache.org/jira/browse/FINERACT-1324>
Benura Abeywardena
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=BLasan>







[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-1296>
FINERACT-1296 <https://issues.apache.org/jira/browse/FINERACT-1296>

Needs to add Liveness & Readiness Probes for fineract server deployment
<https://issues.apache.org/jira/browse/FINERACT-1296>
Benura Abeywardena
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=BLasan>







[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-1302>
FINERACT-1302 <https://issues.apache.org/jira/browse/FINERACT-1302>

Add days in year at loan level
<https://issues.apache.org/jira/browse/FINERACT-1302>
David Yahalomi
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=davidyaha>







[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1156>
FINERACT-1156 <https://issues.apache.org/jira/browse/FINERACT-1156>

SQL injection error with Run Reports
<https://issues.apache.org/jira/browse/FINERACT-1156>
Manthan Surkar
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=manthan>







[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-1295>
FINERACT-1295 <https://issues.apache.org/jira/browse/FINERACT-1295>

Log only WARN & ERR but not INFO anymore
<https://issues.apache.org/jira/browse/FINERACT-1295>
Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger>







[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1138>
FINERACT-1138 <https://issues.apache.org/jira/browse/FINERACT-1138>

Swagger UI should run "try it out" queries against the server where it is
hosted <https://issues.apache.org/jira/browse/FINERACT-1138>
Petri Tuomola
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ptuomola>







[image: New Feature] <https://issues.apache.org/jira/browse/FINERACT-1285>
FINERACT-1285 <https://issues.apache.org/jira/browse/FINERACT-1285>

Upload Credit Report to ThitsaWorks CB
<https://issues.apache.org/jira/browse/FINERACT-1285>
Rahul Pawar
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rrpawar>







[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1311>
FINERACT-1311 <https://issues.apache.org/jira/browse/FINERACT-1311>

SavingsAccount getClosedOnDate nullpointer
<https://issues.apache.org/jira/browse/FINERACT-1311>
Zoltán Nébli
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ezolnbl>







___
Michael Vorburger
http://www.vorburger.ch

Re: Release branch 1.5.0

[Michael Vorburger]

On Mon, 8 Mar 2021, 23:38 Ed Cable,  wrote:

> Looks like Michael plowed through several of the outstanding ones :) Jose
> Alberto from Fintecheando is going to review
> https://github.com/apache/fineract/pull/1644
>
> Ed
>
> On Mon, Mar 8, 2021 at 2:35 PM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> Hi Ed,
>>
>> ... no problem... a day here or day I think doesn't matter. I have myself
>> a new mini task (to document the new external JAR drop-in feature).
>>
>
Aleks, re. documenting the new external JAR drop-in feature, see
https://github.com/apache/fineract/pull/1658 (which is NOT blocking the
release, of course; review and merge whenever).

I will follow those PRs you mentioned and open the release branch when they
>> are ready.
>>
>> Thanks for getting more people on board...
>>
>> Cheers,
>>
>> Aleks
>>
>>
>> On Mon, Mar 8, 2021 at 9:22 PM Ed Cable  wrote:
>>
>>> Aleks,
>>>
>>> Thanks for continuing to drive on this. I have reached out to some other
>>> developers to review #1646 as well as #1623 for the failing build.
>>>
>>> I'm also working with the team at Finflux to do a review of
>>> https://github.com/apache/fineract/pull/1562
>>>
>>> Likewise, still trying to get a review of
>>> https://github.com/apache/fineract/pull/1644
>>>
>>> I would think https://github.com/apache/fineract/pull/1653 would be
>>> another simple review - @Manthan Surkar  can
>>> you take a look.
>>>
>>> It would be nice to include all of the above as this release would
>>> continue a healthy number of significant external contributions from
>>> partners and the like, strong momentum towards an upstream development
>>> model :)
>>>
>>> Ed
>>>
>>> On Mon, Mar 8, 2021 at 2:30 AM Aleksandar Vidakovic <
>>> chee...@monkeysintown.com> wrote:
>>>
 Hi everyone,

 ... I'd like to create the 1.5.0 release branch somewhen today. Before
 I can do that I need someone to review #1646 (FINERACT-1177).

 Could you also give me some feedback on which one of the other 16
 currently open PRs are ready. I'd suggest that anything (issues, PRs) that
 has no feedback in the next 24h moves to release 1.6.0 (again, no worries,
 the release process starts somewhat immediately after this one). Reminder:
 we have to get a security fix out of the door hence the urgency.

 Thanks again for your help.

 Cheers,

 Aleks

>>>
>>>
>>> --
>>> *Ed Cable*
>>> President/CEO, Mifos Initiative
>>> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>>>
>>> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>>>   
>>>
>>>
>
> --
> *Ed Cable*
> President/CEO, Mifos Initiative
> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>   
>
>

Re: GSOC 2021

[Michael Vorburger]

Abhishek,

Where exactly did you see that "Upgrade Fineract 1.x to Java 11 and Upgrade
Dependencies to latest versions" is a GSOC 2021 project?

That project is largely finished and not available anymore and should be
removed from wherever you still saw it listed.

Please let us know where you saw that so that we can clean that up.

Tx,
M.


On Mon, 15 Feb 2021, 17:00 Saransh Sharma,  wrote:

> Think its already upgraded if you run Fineract 1.x it does work with Java
> 11 don’t know if the upgrade is about code upgrade also.
>
> Maybe the upgrade is about something else.
>
> > On 15-Feb-2021, at 3:32 PM, Abhishek Shukla 
> wrote:
> >
> > Hey,
> >  I am Abhishek Kumar Shukla final year student from the United
> College of Engineering and Research Allahabad India.
> >  Recently I started web development, so right now know only the
> basics of HTML, CSS, and JS. But I have > 2 years of experience in Shopify
> or can say in eCommerce and Development.
> >  I also have less experience with open source contributions but
> I hope with the help of you I can overcome every issue/problem.
> >  This year also I am thinking to take part in GSOC so every
> suggestion will be valuable and helpful.
> >  I'm interested in the following idea & would like to start
> working as soon as possible on these:-
> >  Upgrade Fineract 1.x to Java 11 and Upgrade
> Dependencies to latest versions
> >  Kindly let me know where can I get setup documentation/code
> repository etc.
> > Thanks & Regards,
> > Abhishek Kr Shukla
>
>

Fwd: [jira] Subscription: Fineract Resolved Last 2 Weeks

[Michael Vorburger]

Whoot whoot - since the last such email 2 weeks ago, the following 7 issues
got fixed; thanks Benura, we appreciate your contributions very much:

-- Forwarded message -
From: 
Date: Fri, Feb 5, 2021 at 2:02 AM
Subject: [jira] Subscription: Fineract Resolved Last 2 Weeks
To: 




Issue Subscription
Filter: Fineract Resolved Last 2 Weeks
<https://issues.apache.org/jira/issues/?filter=12349982> (7 issues)
Subscriber: vorburger
T Patch Info Key Summary Assignee Reporter P Status Resolution Created Updated
Due Development
[image: Task] <https://issues.apache.org/jira/browse/FINERACT-1292>
FINERACT-1292 <https://issues.apache.org/jira/browse/FINERACT-1292>

Needs to add ReadinessProbe for MySql pod
<https://issues.apache.org/jira/browse/FINERACT-1292>
Benura Abeywardena
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=BLasan> Benura
Abeywardena
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=BLasan> [image:
Minor] Resolved Fixed 14/Jan/21 28/Jan/21 15/Jan/21
[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-1300>
FINERACT-1300 <https://issues.apache.org/jira/browse/FINERACT-1300>

Needs to add init-container to check MYSQL server is up and running for
Fineract server <https://issues.apache.org/jira/browse/FINERACT-1300>
Benura Abeywardena
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=BLasan> Benura
Abeywardena
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=BLasan> [image:
Minor] Closed Fixed 20/Jan/21 28/Jan/21
[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-1301>
FINERACT-1301 <https://issues.apache.org/jira/browse/FINERACT-1301>

Need to add resource limitations to fineract & mysql deployments
<https://issues.apache.org/jira/browse/FINERACT-1301>
Benura Abeywardena
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=BLasan> Benura
Abeywardena
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=BLasan> [image:
Major] Resolved Fixed 21/Jan/21 28/Jan/21 28/Jan/21
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1294>
FINERACT-1294 <https://issues.apache.org/jira/browse/FINERACT-1294>

Error in volume mounting in mysql 5.7 container
<https://issues.apache.org/jira/browse/FINERACT-1294>
Benura Abeywardena
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=BLasan> Benura
Abeywardena
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=BLasan> [image:
Blocker] Resolved Fixed 16/Jan/21 23/Jan/21 23/Jan/21
[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-1075>
FINERACT-1075 <https://issues.apache.org/jira/browse/FINERACT-1075>

Error Prone: Enable JdkObsolete Check
<https://issues.apache.org/jira/browse/FINERACT-1075>
Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> Awasum
Yannick <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=awasum>
[image:
Major] Resolved Fixed 04/Jul/20 23/Jan/21
[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-1297>
FINERACT-1297 <https://issues.apache.org/jira/browse/FINERACT-1297>

Upgrade Google ErrorProne code quality scanner tool from 2.4.0 to 2.5.1
<https://issues.apache.org/jira/browse/FINERACT-1297>
Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Major] Resolved Fixed 17/Jan/21 23/Jan/21
[image: New Feature] <https://issues.apache.org/jira/browse/FINERACT-1285>
FINERACT-1285 <https://issues.apache.org/jira/browse/FINERACT-1285>

Upload Credit Report to ThitsaWorks CB
<https://issues.apache.org/jira/browse/FINERACT-1285>
Rahul Pawar
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rrpawar> Rahul
Pawar <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rrpawar>
[image:
Major] Resolved Implemented 10/Jan/21 02/Feb/21
You may edit this subscription here
<https://issues.apache.org/jira/secure/EditSubscription!default.jspa?subId=23321=12349982>.


This message was sent by Atlassian Jira (v8.3.4#803005-sha1:1f96e09)
[image: Atlassian logo]

Re: Fineract 1.5.0 release branch

[Michael Vorburger]

Hello everyone,

We currently have 111 open issues with Fix Version 1.5.0, see
https://issues.apache.org/jira/issues/?jql=project%20%3D%20%22Apache%20Fineract%22%20AND%20resolution%20is%20EMPTY%20and%20fixVersion%20%3D%201.5.0%20%20ORDER%20by%20status%20DESC%2C%20priority%20DESC%2C%20updated%20DESC

Could we invite any active contributors who have open issues with Fix
Version 1.5.0 assigned to yourself EITHER link them to
https://issues.apache.org/jira/browse/FINERACT-1305 if you are actively
working on them and about to raise a PR, OR remove the 1.5.0 fix version if
it's not going to make it for this next release? (I've just done this for
all issues that were assigned to me.)

Note that the way that this process (has to) work is that only active
contributors set Fix Versions; so this is about "I can commit to fixing
XYZ" and NOT about "I would like XYZ to be fixed for XYZ - but cannot fix
it myself (or pay someone to fix it for me)"... otherwise we would probably
never ship.

The Release Manager (RM, Aleks) will just remove the Fix Version 1.4.0 for
anything that doesn't make it, as per
https://cwiki.apache.org/confluence/display/FINERACT/How+to+Release+Apache+Fineract
.

Best,
M.
_______
Michael Vorburger
http://www.vorburger.ch

On Tue, Jan 26, 2021 at 2:09 PM Aleksandar Vidakovic <
chee...@monkeysintown.com> wrote:

> Hi everyone,
>
> Based on our "How to Release Apache Fineract" process documented at
> https://cwiki.apache.org/confluence/x/DRwIB :
>
> I will create a 1.5.0 branch off develop in our git repository at
> https://github.com/apache/fineract on Wednesday, February 10, 2020.
>
> The release tracking umbrella issue for tracking all activity in JIRA is
> https://issues.apache.org/jira/browse/FINERACT-1305 for this Fineract
> 1.5.0.
>
> If you have any work in progress that you like to see included in this
> release, please add "blocking" links to the release JIRA issue.
>
> I am the release manager for this release.
>
> Cheers,
>
> Aleks
>

Re: Feedback on issue #1222

[Michael Vorburger]

go for it!

On Sun, Feb 7, 2021 at 11:13 AM Benura Abeywardena 
wrote:

> Hi,
>
> I would like to take up the above issue (
> https://issues.apache.org/jira/browse/FINERACT-1222?filter=12349022). And
> need a confirmation on this issue whether it's still valid or not and
> someone has started working on it.
>
> Thanks
>

FINERACT-1052 pull/1536 reviewers?

[Michael Vorburger]

Hello,

Are there any active contributors willing to review
https://github.com/apache/fineract/pull/1536 for
https://issues.apache.org/jira/browse/FINERACT-1052? Does that LGTY?

BTW starting to review PRs from other contributors is a great way for new
contributors to show interest in future promotion to committer status! ;-)

M.
___
Michael Vorburger
http://www.vorburger.ch

Fwd: [jira] Subscription: Fineract Resolved Last Week

[Michael Vorburger]

Whoot whoot - 4 more issues resolved and merged within the last 1 week, see
below!

We also have a lot of 3rd party dependency updates
 going
in, thanks to automation with Renovate Bot.

More PRs are under review and coming up next week.


-- Forwarded message -
From: 
Date: Fri, Jan 22, 2021 at 2:02 AM
Subject: [jira] Subscription: Fineract Resolved Last Week
To: 




Issue Subscription
Filter: Fineract Resolved Last Week
 (4 issues)
Subscriber: vorburger
T Patch Info Key Summary Assignee Reporter P Status Resolution Created Updated
Due Development
[image: Bug] 
FINERACT-1290 

Unnecessary/wrong accrual posting during loan disbursement

Avik Ganguly
 Anu
Omotayo
 [image:
Blocker] Resolved Fixed 14/Jan/21 21/Jan/21
[image: Task] 
FINERACT-1288 

Commands for creating & resetting kubernetes cluster needs to be corrected

Benura Abeywardena
 Benura
Abeywardena
 [image:
Minor] Resolved Fixed 11/Jan/21 15/Jan/21
[image: Task] 
FINERACT-1292 

Needs to add ReadinessProbe for MySql pod

Benura Abeywardena
 Benura
Abeywardena
 [image:
Minor] Resolved Implemented 14/Jan/21 21/Jan/21 15/Jan/21
[image: Improvement] 
FINERACT-734 

Credit Bureau Integration Phase 3

Rahul Pawar
 Nikhil
Pawar 
[image:
Major] Resolved Fixed 19/Mar/19 17/Jan/21
You may edit this subscription here
.


This message was sent by Atlassian Jira (v8.3.4#803005-sha1:1f96e09)
[image: Atlassian logo]

Re: Log only WARN & ERR but not INFO anymore (FINERACT-1295)

[Michael Vorburger]

Given that nobody seems to have voiced any objections to this here (please
do if you disagree with this!), and that there don't seem to be other
active committers reviewing PRs at present, I'll self-merge
https://github.com/apache/fineract/pull/1495 for
https://issues.apache.org/jira/browse/FINERACT-1295 in 3 days.

On Sun, Jan 17, 2021 at 12:39 PM Michael Vorburger 
wrote:

> Hello everyone,
>
> I'm curious if you all are FOR or AGAINST
> https://github.com/apache/fineract/pull/1495 for
> https://issues.apache.org/jira/browse/FINERACT-1295?
>
> I personally like it, but I don't want to "impose" this visible change of
> default log level that you would all notice - if there is a majority here
> who LOVES staring at INFO level logs... ;-) I personally find them useless,
> and like the "cleanliness" you get with that PR.
>
> Let's conclude if we either merge or abandon that PR; please comment on
> FINERACT-1295, PR #1495, or here.
>
> Thanks!
> M.
>
> ___
> Michael Vorburger
> http://www.vorburger.ch
>

Log only WARN & ERR but not INFO anymore (FINERACT-1295)

[Michael Vorburger]

Hello everyone,

I'm curious if you all are FOR or AGAINST
https://github.com/apache/fineract/pull/1495 for
https://issues.apache.org/jira/browse/FINERACT-1295?

I personally like it, but I don't want to "impose" this visible change of
default log level that you would all notice - if there is a majority here
who LOVES staring at INFO level logs... ;-) I personally find them useless,
and like the "cleanliness" you get with that PR.

Let's conclude if we either merge or abandon that PR; please comment on
FINERACT-1295, PR #1495, or here.

Thanks!
M.

_______
Michael Vorburger
http://www.vorburger.ch

Re: FIneract Database Setup (Managed Database on Digital Ocean)

[Michael Vorburger]

Airsay, we would *LOVE* contributions to the documentation about this and
similar issues, from you and anyone else reading this. Contributions to doc
are as important as code features & bug fixes! ;)

And just in terms of WHERE to contrib docs, in addition to Wiki and the
README that James already pointed out, I'd like to highlight
https://github.com/apache/fineract/tree/develop/fineract-doc/src/docs/en ...

What we're missing re. the (new) /fineract-doc/ module is
https://issues.apache.org/jira/browse/FINERACT-1253. If there is anyone
interested in working on that front, go for it!!

On Thu, Jan 7, 2021 at 10:40 PM James Dailey  wrote:

> Airsay
>
> I think this could either be added to the wiki pages:
> https://cwiki.apache.org/confluence/display/FINERACT/Fineract+User+Zone
> <https://cwiki.apache.org/confluence/display/FINERACT/Fineract+User+Zone>
> maybe a sub-page about multi-tenancy,  tenant naming and connection
> parameters?
>
> or (perhaps better) directly to the top level README, if it is something
> that will persist for several releases.
> https://github.com/apache/fineract/blob/develop/README.md
> <https://github.com/apache/fineract/blob/develop/README.md>
>
> You may also want to look at the wiki page "hosting fineract" where info
> about Digital Ocean hosting would be useful.
>
> https://cwiki.apache.org/confluence/display/FINERACT/Hosting+Experiences+from+Partners
> <https://cwiki.apache.org/confluence/display/FINERACT/Hosting+Experiences+from+Partners>
>
> Will you suggest some changes and content?
>
> On Thu, Jan 7, 2021 at 9:10 AM Airsay Longcon 
> wrote:
>
>> Hello everyone
>> How can one add this as part of the documentation for Fineract. I'm
>> certain there'd be a lot of requests similar to this in the future.
>>
>> > On 6 Jan 2021, at 05:58, Chairul Akmal 
>> wrote:
>> >
>> > Great!
>> >
>> > Thanks Petri for your answer. Yes, actually that was what I were
>> looking for.
>> >
>> > Regards
>> > Chairul
>> >
>> >> On 2021/01/05 23:00:04, Petri Tuomola  wrote:
>> >> Hi Chairul
>> >>
>> >> I hope I understood your question correctly - but if you are asking
>> where can you set the connection parameters for the different tenant
>> databases, please look at the table tenant_server_connections on the
>> database fineract_tenants
>> >>
>> >> The columns schema_server, schema_server_port, schema_name,
>> schema_connection_parameters in that table are used to construct the
>> connection string for each tenant database as follows:
>> >>
>> >>String jdbcUrl =
>> this.driverConfig.constructProtocol(tenantConnectionObj.getSchemaServer(),
>> >>tenantConnectionObj.getSchemaServerPort(),
>> tenantConnectionObj.getSchemaName(),
>> >>tenantConnectionObj.getSchemaConnectionParameters());
>> >>
>> >> So if you want to change the server / schema name for a specific
>> tenant, try updating the relevant row in the table fineract_tenants.
>> >>
>> >> Hope this helps
>> >>
>> >> Regards
>> >> Petri
>> >>
>> >>>> On 5 Jan 2021, at 8:55 PM, Chairul Akmal 
>> wrote:
>> >>>
>> >>> Hi Michael,
>> >>>
>> >>> Thank you so much for your response.
>> >>>
>> >>> I think my question was not clear. Sorry about that. What I meant was
>> the database (DB) name for the default tenant itself, "fineract_default".
>> Unlike for "fineract_tenants" that accept database url (which contains the
>> DB name) as env var, FINERACT_DEFAULT_TENANTDB only accept hostname and
>> port. So, my question is rather, does fineract require the tenant database
>> to be named "fineract_default"? Is there a way to use different tenant DB
>> name without changing the codebase?
>> >>>
>> >>> Thank you for understanding.
>> >>>
>> >>> Update: Thankfully, I have managed to connect the docker image with
>> database (by naming the tenant DB `fineract_default`). There are some
>> problem with database migrations where V1 failed with `(SQL State: 42S02 -
>> Error Code: 1051)`, looks like related to the jdbc driver. But this is a
>> different problem. :)
>> >>>
>> >>> Cheers,
>> >>> Chairul
>> >>>
>> >>> On 2021/01/04 17:32:11, Michael Vorburger  wrote:
>> >>>> Chairul,
>> >&

Fwd: [jira] Subscription: Fineract Resolved Last Week

[Michael Vorburger]

Please note the 5 issues below fixed last week. Our community's Thanks go
to existing contributors Cedric, Rahul and (whoot whoot) new first time
contributor David Yahalomi - welcome!! Also Benura Abeywardena, who
normally should automatically appear in the next such announcement e.g. for
his just merged FINERACT-1294
<https://issues.apache.org/jira/browse/FINERACT-1294> (which is not yet
listed below). Keep contributions coming - together we're at our best.

-- Forwarded message -
From: 
Date: Fri, Jan 15, 2021 at 2:01 AM
Subject: [jira] Subscription: Fineract Resolved Last Week
To: 




Issue Subscription
Filter: Fineract Resolved Last Week
<https://issues.apache.org/jira/issues/?filter=12349018> (5 issues)


Subscriber: vorburger
T Patch Info Key Summary Assignee Reporter P Status Resolution Created Updated
Due Development
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1281>
FINERACT-1281 <https://issues.apache.org/jira/browse/FINERACT-1281>

No "releaseInteropTransferHandler" command handler
<https://issues.apache.org/jira/browse/FINERACT-1281>
Cedric Khin
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Sugiuro> Cedric
Khin <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Sugiuro>
[image:
Major] Resolved Fixed 14/Dec/20 10/Jan/21

[image: Sub-task] <https://issues.apache.org/jira/browse/FINERACT-887>
FINERACT-887 <https://issues.apache.org/jira/browse/FINERACT-887>

FINERACT-850 <https://issues.apache.org/jira/browse/FINERACT-850> FLAKY
org.apache.fineract.integrationtests.FixedDepositTest >
testMaturityAmountForDailyCompoundingAndMonthlyPosting_With_365_Days FAILED
<https://issues.apache.org/jira/browse/FINERACT-887>
Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Major] Resolved Fixed 13/Apr/20 12/Jan/21

[image: Sub-task] <https://issues.apache.org/jira/browse/FINERACT-1110>
FINERACT-1110 <https://issues.apache.org/jira/browse/FINERACT-1110>

FINERACT-734 <https://issues.apache.org/jira/browse/FINERACT-734> Token
Module <https://issues.apache.org/jira/browse/FINERACT-1110>
Rahul Pawar
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rrpawar> Rahul
Pawar <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rrpawar>
[image:
Major] Resolved Implemented 07/Aug/20 10/Jan/21

[image: Sub-task] <https://issues.apache.org/jira/browse/FINERACT->
FINERACT- <https://issues.apache.org/jira/browse/FINERACT->

FINERACT-734 <https://issues.apache.org/jira/browse/FINERACT-734> Fetch
Credit Report from ThitsaWorks CB
<https://issues.apache.org/jira/browse/FINERACT->
Rahul Pawar
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rrpawar> Rahul
Pawar <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rrpawar>
[image:
Major] Resolved Delivered 07/Aug/20 10/Jan/21

[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1286>
FINERACT-1286 <https://issues.apache.org/jira/browse/FINERACT-1286>

NullPointerException on calc schedule for floating rate loans
<https://issues.apache.org/jira/browse/FINERACT-1286>
*Unassigned* David Yahalomi
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=davidyaha> [image:
Minor] Resolved Fixed 11/Jan/21 14/Jan/21

You may edit this subscription here
<https://issues.apache.org/jira/secure/EditSubscription!default.jspa?subId=23124=12349018>.


This message was sent by Atlassian Jira (v8.3.4#803005-sha1:1f96e09)
[image: Atlassian logo]

Re: Start with Fineract 1.x or Fineract CN?

[Michael Vorburger]

Giancarlo, re. "Is there a fork of fineract 1.x that is actively
developed?" : Fineract 1.x *IS* actively maintained, on
https://github.com/apache/fineract - in the sense that there are active
maintainers reviewing new contributions from parties interested in seeing
it thrive, ready to invite new committers if anyone worthwhile emerges,
etc. That is the open source way. It does NOT mean "free as in beer", if
you know what I mean (otherwise, look it up online). Some people
unfortunately are sometimes a little confused about how this all really
works... ;-) Forks away from the main project only serve the 1 forked party
instead of the overall community, and do not contribute to the project.

On Sat, 16 Jan 2021, 13:31 Saransh Sharma,  wrote:

> There are many forks out there , not sure if they have made any changes
> outside of what fineract does.
>
>
>
> On Sat, Jan 16, 2021 at 4:49 PM Giancarlo Angulo 
> wrote:
>
>> Is there a fork of fineract 1.x that is actively developed?
>>
>>
>> 
>> Giancarlo Angulo
>> www.onthe8spot.com
>> 
>>
>>
>> On Sat, Jan 16, 2021 at 6:00 PM Saransh Sharma 
>> wrote:
>>
>>>
>>>
>>> > On 15-Jan-2021, at 10:04 PM, Paul Aphivantrakul <
>>> aphivantra...@gmail.com> wrote:
>>> >
>>> > Hello,
>>> >
>>> > To a newcomer doing a fintech startup, does the community recommend
>>> starting with the Fineract 1.x software or the Fineract CN software? I
>>> would say that to me, security and maturity of the software are more
>>> important than having a large and rich set of features as my startup will
>>> likely focus on offering a limited set of financial services at the
>>> beginning. I have also noticed that there is a lot more documentation for
>>> Fineract 1.x and also a lot more developers contributing to the Fineract
>>> 1.x repository than on the Fineract CN repository. At this point, I am
>>> leaning more towards using Fineract 1.x, but I also like the modular aspect
>>> of Fineract CN.
>>> >
>>> > Thank you,
>>> >
>>> > Paul
>>>
>>> Hey Paul, its fair to say Fineract CN is dead , the one who will say
>>> that its not are promoting invalid information, I would nothing on facts
>>> but just talks.
>>>
>>> We have started the work over migrating these service keeping in mind
>>> for inbuilt security with key focus on developer ready.
>>>
>>> The key idea is that any FI could develop in any lang or framework can
>>> utilise the today framework like we have in built consensus layer that
>>> keeps the data consistency in place.
>>>
>>> Its easier for payment rails to utilise such logs that are immutable.
>>>
>>> Yeah I think Fineract 1.x is there its more solid then Fineract CN .
>>>
>>> If you wish to have more discussion around technology that works for
>>> practical use case reach out to me.
>>>
>>> Thanks
>>
>>
>
> --
>
> Saransh Sharma
> *Research Partner*
> *Muellner Internet Pvt Ltd *
>
>
> --
>
> The idea of separation of me and you is amazing.
>
> --
> *Company Website    **Company Linkedin
> *Company Facebook
> 
>
> This mail is governed by Muellner®  Internet Private Limited's IT policy.
> The information contained in this e-mail and any accompanying documents
> may contain information that is confidential or otherwise protected from
> disclosure. If you are not the intended recipient of this message, or if
> this message has been addressed to you in error, please immediately alert
> the sender by reply e-mail and then delete this message, including any
> attachments. Any dissemination, distribution or other use of the contents
> of this message by anyone other than the intended recipient is strictly
> prohibited. All messages sent to and from this e-mail address may be
> monitored as permitted by applicable law and regulations to ensure
> compliance with our internal policies and to protect our business. E-mails
> are not secure and cannot be guaranteed to be error free as they can be
> intercepted, amended, lost or destroyed, or contain viruses. You are deemed
> to have accepted these risks if you communicate with us by e-mail.
>

Re: list serv norms

[Michael Vorburger]

James your proposal seems to include suggesting that we move the dev@ list
to a fully moderate mode. I don't think we currently are set up like that.
Doing so requires significant investment from a group of people to actively
moderate. I personally have some doubts that we have sufficient critical
mass in this community to actively moderate a mailing list, and think
keeping this list open as-is is simpler - but would be very happy to be
proven wrong. Your other points all do make sense to me - I think it's
great if more "senior" members of the mailing list who have been around the
community a little while can jump to help guide people on any threads from
"newer" community members.

BTW the "traditional" solution used in many other open source projects
would be to "split up" into 2 separate mailing lists - one more focused on
technical discussions for future releases, and one on end-user discussions,
more typically for released versions (but this doesn't have to be a super
hard rule). The "risk" of course is that things could also become a bit
more "fragmented", but maybe that's not a huge issue?

FYI this community actually did have a separate u...@fineract.apache.org
list in the past (+2 years ago; see the archives e.g. here
),
but it went unused; all discussions were only on the dev list. I had
removed the link to it from https://fineract.apache.org in
https://github.com/apache/fineract-site/commit/2a28160dd1767771d887a82583a35f902dcf6740,
to avoid confusion.

What are everyone's thoughts about re-instantiating the user@ list in
parallel to this dev@ list? Perhaps the time is right for that now. It just
needs someone to actually drive doing this; I'm actually not sure if that
list just went "silent" or was actually "deactivated" back then. (I
personally will not drive reviving it, but anyone motivated could step up
to do that.)

On Tue, Dec 22, 2020 at 7:50 AM Saransh Sharma 
wrote:

> + 1 , in fact we could have a dedicated service desk with community
> members supporting each other. That way we can build a pool of updated
> knowledge base.
>
> Most questions come here because there is no filter  or a clear step on
> the website like we could use stackoverflow to post how tos and this is not
> working style questions.
>
>
>
> On Tue, Dec 22, 2020 at 3:39 AM James Dailey 
> wrote:
>
>> Hi all -
>>
>> I am seeing a fair amount of requests for help, and also many "what are
>> you trying to do?" responses from people on the list. As we grow the
>> participation this is normal, but it seems to be clogging up the needed
>> technical discussions.  We need to organize this a bit more.
>>
>> *Proposed: (please give your +1, -1, or Neutral within 72 hrs) *
>>
>> As a group we shall:
>> 1) Send a STANDARD RESPONSE (See below) to all new people to list.  Any
>> new person coming to the list is welcomed with a standard email that
>> includes the links and explanations. The message will include the
>> admonition to ONLY POST once you have read the materials.  see wiki, faq,
>> jira tickets, readme, demo servers, etc.
>>
>> 2) It is also a norm on listservs that people should join, introduce
>> themselves and describe why they are here.   i.e. I am here as a student
>> learning a new skill, I am running a production version and need help, I am
>> looking to build something, I have a major critical bug that is holding
>> back my fintech, and the catch all  "I am here to learn more and maybe
>> participate later".   Until the person has done an introduction of some
>> kind, the list members will keep reminding that person that they need to do
>> so because it provides context.
>>
>> 3) One Subject per email enforced
>> If someone introduces a new topic, that email is rejected by the
>> moderators, with a request that the person start a new thread.
>>
>> 4) Each new email thread contains some context.  Each posting should
>> include what it's about.  i.e. "This is about trying to set up a local
>> instance so I can do some local testing with new features I'm
>> developing"... vs. "I just need to see the functionality, can someone point
>> me to a how to on config" vs. "I have a proposal for how to automate some
>> testing" vs. "I am working on bug issue #xxx".
>>
>> 5) Each email dealing with a bug or issue or question should include the
>> version of software and/or where it was downloaded from.  Hopefully if (1)
>> is handled well, then they know not to download one of the old versions
>> that may be floating around out there.
>>
>> 6) Emails that reference existing bugs, cite a discussion onlist and
>> provide appropriate links to Jira tickets are answered first and with
>> attention.  We encourage this strongly.
>>
>> ---
>> STANDARD RESPONSE #1
>>
>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103094318
>> 

Re: Loading Historical Floating Rate Periods

[Michael Vorburger]

On Mon, Jan 4, 2021 at 5:19 PM David Yahalomi  wrote:

> Hey Bharath,
>
> Thanks for the response.
>
> I've created this PR on our fork -
> https://github.com/hypercore-ai/fineract/pull/10/files
>
> It enables the submission of historic rates with a flag on the floating
> rate PUT request.
> As you've mentioned, the actual work here is testing the effect of such a
> change.
> Do you know if the integration tests are currently testing the scenarios
> you've specified?
>

David, if you raise a PR on https://github.com/apache/fineract/pulls,
you'll quickly see if there is an IT test failure... ;-) don't be shy!

You can mark such a PR as a "Draft" to signal to committers that "I don't
need you to actually look at this for merging, just yet".


> If not, we will soon manually test some of these cases.
>
> Best,
>
> David Yahalomi
> Co-Founder
>
> Rothschild Blvd 3, Tel Aviv-Yafo, Israel
> mobile: + 972 52 817 9787
> email: da...@articode.co
>   
>
> ᐧ
>
> On Mon, Jan 4, 2021 at 4:20 PM Bharath Gowda  wrote:
>
>> Hi David,
>>
>> Sounds interesting and a good feature to be unlocked, validation could be
>> added either because of all the scenarios not tested yet, or there could be
>> specific scenarios not handled at that time.
>>
>> We will have to test as much as scenarios as possible to check if there
>> are any side effects
>>
>> Following are some  important scenarios that could be tested
>> 1. Rescheduling of loans and repay/undo repay scenarios.
>> 2. Interest accruals behaviors on daily interest calculation
>> configuration
>> 3.Tranche loans scenarios
>> 4.Penalty charge scenarios
>>
>> If things are still good, we could push the changes back to the upstream
>> codebase, so that all the people of the community could be benifited from
>> the feature.
>>
>>
>> Regards,
>> Bharath
>> Lead Implementation Analyst | Mifos Initiative
>> Skype: live:cbharath4| Mobile: +91.7019635592
>> http://mifos.org  
>> 
>>
>>
>> On Sun, Jan 3, 2021 at 9:34 PM David Yahalomi  wrote:
>>
>>> Hello all,
>>>
>>> In my current work with Fineract, I've noticed that there is a
>>> constraint in Fineract that prohibits the submission of past periods.
>>>
>>> Does anyone know of a reason for that?
>>> From my testing, after disabling this validation check, it seems that
>>> the rest of the code handles that scenario quite well. Any loans with
>>> interest re-calculation will be updated as it should.
>>>
>>> I'd love to hear your thoughts.
>>>
>>> Best,
>>>
>>> David Yahalomi
>>> Co-Founder
>>>
>>> Rothschild Blvd 3, Tel Aviv-Yafo, Israel
>>> mobile: + 972 52 817 9787
>>> email: da...@articode.co
>>>   
>>> ᐧ
>>>
>>

Re: FIneract Database Setup (Managed Database on Digital Ocean)

[Michael Vorburger]

Chairul,

you're ALMOST ;) there - note how in
https://github.com/apache/fineract/blob/develop/docker-compose.yml#L45
there is BOTH the fineract_tenants_* but ALSO the
FINERACT_DEFAULT_TENANTDB_* env vars? The latter is what you are looking
for!

HTH & makes sense?

M.

PS: Would someone be willing to contribute better documentation about this?
Ideally via a PR to
https://github.com/apache/fineract/blob/develop/README.md, or
https://github.com/apache/fineract/tree/develop/fineract-doc/src/docs/en.

___
Michael Vorburger
http://www.vorburger.ch


On Mon, Jan 4, 2021 at 5:42 PM Chairul Akmal 
wrote:

> Hi folks,
>
> I am a new fineract user and have been recently trying to deploy fineract
> 1.4.0 on Digital Ocean. The plan that I currently have is to deploy
> apache/fineract docker image and connect to managed MySQL database from
> Digital Ocean. However, I have been struggling with connecting fineract
> with the non-local database.
>
> I understand that there are ways to modify the `fineract_tenants` database
> from environmental variables (e.g. in docker-compose.yml), however can I do
> the same with `fineract_default`? The way I see it, `fineract_default` is
> hard-coded a lot in source code and I wanted to modify it, unfortunately I
> can't find any documentations on fineract database setup/schema. I tried
> googling around for old mifos documentations but most of them are
> deprecated or inaccessible anymore.
>
> Cheers,
> Chairul
>

FixedDepositTest is flaky (FINERACT-887)

[Michael Vorburger]

Hello everyone, we need someone to step up to debug and fix
https://issues.apache.org/jira/browse/FINERACT-887... all pull requests and
merged are now blocked because of that problem. Thank You!

Re: Deploy on Fineract.dev GitHub action failure

[Michael Vorburger]

Paul, yeah, as Saransh pointed out.. and additionally you do need a Tenant
as well of course.

Note how https://www.fineract.dev has a link to
https://demo.fineract.dev/fineract-provider/api/v1/clients?tenantIdentifier=default

Hope that helps.


On Thu, 31 Dec 2020, 09:09 Saransh Sharma,  wrote:

> You are missing the path /fineract-provider/ before api
>
> Sent from my iPhone
>
> On 31-Dec-2020, at 12:37 PM, Paul Aphivantrakul 
> wrote:
>
> 
> Hello Michael,
>
> I watched your YouTube video about setting up the demo Fineract server
> here https://www.youtube.com/watch?v=EkCOSjTEtbw
>
> I am having trouble calling the REST API on the Fineract demo website
> https://www.fineract.dev/
>
> I am using Postman to send my GET request. My request is to get the list
> of all the clients as detailed here
> https://demo.mifos.io/api-docs/apiLive.htm#clients_list
>
> URL:
> https://www.fineract.dev/api/v1/clients
>
> Response:
> and I am getting a 404 response
>
> 404
> File not found
>
> 
> The site configured at this address does not
> contain the requested file.
> 
>
> Any help would be much appreciated.
>
> Thank you,
>
> Paul
>
> On Wed, Dec 30, 2020 at 9:50 PM Michael Vorburger 
> wrote:
>
>> Hello,
>>
>> If you have any interest in better understanding the "Deploy on
>> Fineract.dev" GitHub action, and how to "debug" a failure that it had
>> today, check out https://github.com/vorburger/www.fineract.dev/issues/3.
>> TL;DR it's all good again now, it was just a transient one time failure...
>> ;-)
>>
>> BTW if anyone is interested in helping with
>> https://github.com/vorburger/www.fineract.dev/issues/4, don't be shy,
>> and do send PRs for that.
>>
>> Best wishes for 2021 to everyone BTW!
>>
>> Regards,
>> M.
>> ___
>> Michael Vorburger
>> http://www.vorburger.ch
>>
>

Deploy on Fineract.dev GitHub action failure

[Michael Vorburger]

Hello,

If you have any interest in better understanding the "Deploy on
Fineract.dev" GitHub action, and how to "debug" a failure that it had
today, check out https://github.com/vorburger/www.fineract.dev/issues/3.
TL;DR it's all good again now, it was just a transient one time failure...
;-)

BTW if anyone is interested in helping with
https://github.com/vorburger/www.fineract.dev/issues/4, don't be shy, and
do send PRs for that.

Best wishes for 2021 to everyone BTW!

Regards,
M.
_______
Michael Vorburger
http://www.vorburger.ch

Re: [Mifos-developer] Fwd: Error on the webserver

[Michael Vorburger]

On Wed, Dec 16, 2020 at 9:17 AM Awasum Yannick  wrote:

> Hi Emmanuel,
>
> On Mon, Dec 14, 2020 at 8:28 PM Emmanuel Njoku  wrote:
>
>> Dear All,
>>
>> please I need an assist on the following for MIFOS
>>
>> Unable to delete fineract-provider folder the error is Destination Path
>> Too Long.
>>
>
> I dont understand where you are deploying or what you are trying to do.
>
>>
>> The second error message is after cloning
>> https://github.com/openMF/incubator-fineract.git and build successfully
>> and deployed on the apache tomcat 7.0.103. I am unable to open
>> https://localhost:8443/fineract-provider/api-docs/apiLive.htm and
>> https://localhost:8443/fineract-provider/swagger-ui/index.html. The
>> error message is
>>
>
> https://github.com/openMF/incubator-fineract is no longer active and is
> in archive mode. Please use https://github.com/apache/fineract as the
> basis of your backend. Maybe from there you can integrate Pentaho on your
> end. Its also a good idea to branch from the 1.4.0 tag on github. There is
> an already build and released Fineract 1.4.0 on the website:
> http://fineract.apache.org/
>
> If you are waiting for the Latest Mifos Release with Pentaho built on top
> of the latest Fineract release then you will have to ask the folks at Mifos
> for a timeline or if they plan on making a release.
>

Re. Pentaho, please also note https://github.com/vorburger/fineract-pentaho.
(FYI it's currently a little cumbersome to install on Windows; watch
https://github.com/vorburger/fineract-pentaho/issues/2 for an improvement
for that I'll work on when I have some time.)


>
> Let us know how we can help you.
>
> Thanks.
> Awasum
>
>>
>> HTTP Status 404 – Not Found
>> --
>>
>> *Type* Status Report
>>
>> *Message* /fineract-provider/api-docs/apiLive.htm
>>
>> *Description* The origin server did not find a current representation
>> for the target resource or is not willing to disclose that one exists.
>>
>> On Mon, Dec 14, 2020 at 2:02 PM Bharath Gowda  wrote:
>>
>>> Thank you, Petri and Michael, for your help
>>>
>>> @Michael
>>>
>>> I just want to build the later Fineract war to test and implement 2FA
>>> for one of our projects.
>>> I will surely try out those commands once the email issues are resolved.
>>> and thank you for honest and right answers always, which is
>>> really helpful and making us learn and know more every time :)
>>>
>>>
>>>
>>>
>>>
>>>
>>> Regards,
>>> Bharath
>>> Lead Implementation Analyst | Mifos Initiative
>>> Skype: live:cbharath4| Mobile: +91.7019635592
>>> http://mifos.org  <http://facebook.com/mifos>
>>> <http://www.twitter.com/mifos>
>>>
>>>
>>> On Sat, Dec 12, 2020 at 3:20 AM Michael Vorburger 
>>> wrote:
>>>
>>>> Petri, thanks! WOuld you like to capture this in a new JIRA, for
>>>> future reference?
>>>>
>>>> Bharat, I just want to make extra sure that there is no
>>>> misunderstanding about what you are trying to achieve here: Are you a)
>>>> trying to get /actuator/health to work with "gradlew build
>>>> -Ptwofactor=enabled", OR b) do you really just want to locally build the
>>>> very latest Fineract WAR from the develop branch in git? Because it's the
>>>> latter, then you can just skip running the tests locally, so like by using
>>>> "gradlew war -Ptwofactor=enabled" instead of "build". (You can even make it
>>>> a little faster by using "gradlew -x spotlessJava -x spotlessJavaCheck -x
>>>> compileTestJava war".)
>>>>
>>>> But before you ;) retry, note
>>>> https://issues.apache.org/jira/browse/FINERACT-1280 where Francis
>>>> pointed out that FINERACT-1070 was not correctly fixed; watch that issue
>>>> for updates.
>>>>
>>>> On Wed, Dec 9, 2020 at 11:58 PM Petri Tuomola 
>>>> wrote:
>>>>
>>>>> Hi Bharath
>>>>>
>>>>> I looked at this in September / October, and back then my findings
>>>>> were as below:
>>>>>
>>>>> -
>>>>>
>>>>> If you look at securityContext, you can see that
>>>>> TenantAwareTenantIdentifierFilter is only applied in the “oauth”
>>>>> profile. It doesn’t get used in the basicauth scenario.
>>>&

Re: Fineract google container for payment hub?

[Michael Vorburger]

Kristóf, the truth is that there actually simply isn't any Fineract 1.4 on
a public the Google Container (Docker) Registry anywhere... ;-)

For https://www.fineract.dev, as per the earlier thread James posted, I
rebuild it from develop (on every commit to GitHub, fully automated) and
push it to Google Container Registry (because Google Cloud doesn't like to
read directly from Docker Hub). That registry is internal to
https://www.fineract.dev and not public, because normally people don't need
this, as it's also available on https://hub.docker.com/r/apache/fineract. I
could open it up with 1 click (but would then need to watch costs for
egress a bit), but.. is that what you're looking for, would this help you?
I get that impression you want a "latest stable" release, so you want a 1.4
tag on a registry.

We actually don't even have a 1.4 on Docker Hub, yet. I had created
https://issues.apache.org/jira/browse/FINERACT-1164 about it a while back.
You basically want that, but on a publicly available Google Cloud Container
Registry, right? But if we do something like this as a project, it should
be automated for all release tags, not a "manual" 1.4.0 I build and push,
that's nonsense. I can try looking into how hard that would over the coming
big break, if that would help you a lot? Are there others reading this who
would use such released (1.4, future 1.5) container images, if they were
available on some repository? Whether Docker Hub or on Google Cloud
registry probably doesn't actually matter, does it, as long as you can
easily "docker pull" it?

But isn't it simpler for you to simply rebuild from a Git tag inside your
Google Cloud project (like I do for https://www.fineract.dev, but from
develop)? It's not hard. Or am I missing something, or are there any tips I
can share? Again, to be it seems fairly trivial to just selb build whatever
you need, but do let me know if I'm perhaps underestimating the complexity
this causes for end-users here?


On Wed, Dec 9, 2020 at 5:46 PM Kristóf Józsa  wrote:

> Hi Michael,
>
> the question is of course, whether we can get access to the docker images
> of the latest Fineract 1.4 from the Google docker registry. What do we need
> to be able to pull those images and use them in the Mifos Mojaloop Lab
> environments?
>
> thanks,
> K
>
>
> On Wed, Dec 9, 2020 at 5:32 PM James Dailey 
> wrote:
>
>> The team at DPC is working on the mifos payment hub integration with
>> fineract as part of an ongoing demonstration of the full Mifos/Fineract
>> payments lab. (more info on the mifos website)
>>
>> To do that they've been using a snapshot of the dev branch but are
>> shifting to a "latest stable" release strategy.  This is for Fineract1.x at
>> this point. i.e. we're moving to upstream.
>>
>> @Michael Vorburger   had mentioned on a thread about
>> docker --> google container registry:
>>
>> http://mail-archives.apache.org/mod_mbox/fineract-dev/202011.mbox/%3cCALiX4iaw_b-PkuSVMTr=caQf2SzSO=aqtwt8evemf_sduwg...@mail.gmail.com%3e
>> <http://mail-archives.apache.org/mod_mbox/fineract-dev/202011.mbox/%3cCALiX4iaw_b-PkuSVMTr=caQf2SzSO=aqtwt8evemf_sduwg...@mail.gmail.com%3e>
>>
>> The need is to pull a stable blob that could be pushed and hosted on
>> Azure or AWS.
>>
>> @kristof - please ask your questions here on list.
>>
>> Thanks,
>> @jdailey 
>>
>>

Re: 2 Factor Authentication Help

[Michael Vorburger]

s Report
> 
>   Description
>
>  The origin server did not find a current representation for the
> target reso
> urce or is not willing to disclose that one exists.
> 
> Apache Tomcat/9.0.40
>   
> 
> at
> org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:39)
> at org.junit.jupiter.api.Assertions.fail(Assertions.java:117)
> at
> org.apache.fineract.integrationtests.common.Utils.awaitSpringBootActu
> atorHealthyUp(Utils.java:105)
> at
> org.apache.fineract.integrationtests.common.Utils.loginIntoServerAndG
> etBase64EncodedAuthenticationKey(Utils.java:119)  "
>
> Regards,
> Bharath
> Lead Implementation Analyst | Mifos Initiative
> Skype: live:cbharath4| Mobile: +91.7019635592
> http://mifos.org  <http://facebook.com/mifos>
> <http://www.twitter.com/mifos>
>
>
> On Thu, Dec 3, 2020 at 9:53 PM Bharath Gowda  wrote:
>
>> Thank you Michael :)
>>
>>
>>
>> Regards,
>> Bharath
>> Lead Implementation Analyst | Mifos Initiative
>> Skype: live:cbharath4| Mobile: +91.7019635592
>> http://mifos.org  <http://facebook.com/mifos>
>> <http://www.twitter.com/mifos>
>>
>>
>> On Thu, Dec 3, 2020 at 8:50 PM Michael Vorburger 
>> wrote:
>>
>>> Bharath,
>>>
>>> I have fixed https://issues.apache.org/jira/browse/FINERACT-1070 for
>>> you. - Enjoy!
>>>
>>> M.
>>> ___
>>> Michael Vorburger
>>> http://www.vorburger.ch
>>>
>>>
>>> On Mon, Nov 30, 2020 at 3:30 PM Bharath Gowda  wrote:
>>>
>>>> **Update**
>>>> I see an issue already reported on the same by Francis. so it is a bug
>>>> :)
>>>>
>>>> https://issues.apache.org/jira/browse/FINERACT-1070
>>>>
>>>> Would appreciate it if any developer could help in fixing this issue.
>>>>
>>>>
>>>> Regards,
>>>> Bharath
>>>> Lead Implementation Analyst | Mifos Initiative
>>>> Skype: live:cbharath4| Mobile: +91.7019635592
>>>> http://mifos.org  <http://facebook.com/mifos>
>>>> <http://www.twitter.com/mifos>
>>>>
>>>>
>>>> On Mon, Nov 30, 2020 at 7:51 PM Bharath Gowda  wrote:
>>>>
>>>>> Hi Michael,
>>>>>
>>>>> It looks like it is reading the configurations from External Services,
>>>>> However, when we change the value of the 'port' parameter, the System is
>>>>> still by default referring to port 25.
>>>>>
>>>>> "Sending the email to the following server failed: smtp.gmail.com:*25*
>>>>> "
>>>>>
>>>>> I Changed the port to *587 *but I still got the above error. so
>>>>> wanted to understand if this is hardcoded or reading from somewhere else
>>>>> which I am not able to locate.
>>>>>
>>>>> But am sure the 'host' parameter is reading from External Services
>>>>> only as any change done to that, I can notice the same in the log.
>>>>>
>>>>> If this looks like a bug let me know, I will raise a JIRA ticket for
>>>>> the same.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Regards,
>>>>> Bharath
>>>>> Lead Implementation Analyst | Mifos Initiative
>>>>> Skype: live:cbharath4| Mobile: +91.7019635592
>>>>> http://mifos.org  <http://facebook.com/mifos>
>>>>> <http://www.twitter.com/mifos>
>>>>>
>>>>>
>>>>> On Sun, Nov 29, 2020 at 1:08 AM Michael Vorburger 
>>>>> wrote:
>>>>>
>>>>>> On Fri, Nov 27, 2020 at 7:31 PM Bharath Gowda 
>>>>>> wrote:
>>>>>>
>>>>>>> Hello Everyone,
>>>>>>>
>>>>>>> I am working on testing and documenting 2 factor authentication
>>>>>>> usecases and need some help on configurations
>>>>>>>
>>>>>>> I was able to successfully build the war file with 2FA enabled and I
>>>>>>> am getting a login screen to select a way to receive the authentication
>>>>>>> token.
>>>>>>>
>>>>>>> 
>>>>>>>
>>>>>>> However, the Sending Email is failing with the default email
>>>>>>> settings in the system.
>>>>>>> "a response, re-throwing to the HTTP container
>>>>>>> org.apache.fineract.infrastructure.core.service.PlatformEmailSendException:
>>>>>>> org.apache.commons.mail.EmailException: Sending the email to the 
>>>>>>> following
>>>>>>> server failed : smtp.gmail.com:25
>>>>>>> at
>>>>>>> org.apache.fineract.infrastructure.core.service.GmailBackedPlatformEmailService.sendDefinedEmail(GmailBackedPlatformEmailService.java:81)"
>>>>>>> 
>>>>>>>
>>>>>>> Need some insight on how to configure Email in external services.
>>>>>>> how and from where we can get the configuration details which will
>>>>>>> work
>>>>>>>
>>>>>>
>>>>>> Bharath, I'm not sure I fully understand the exact question you are
>>>>>> asking.. it's reading the email server configuration from that System /
>>>>>> External Services, and you "just" need to replace the dummy default 
>>>>>> (shown
>>>>>> in your screenshot) with a "real" (proper) SMTP email server. Does this
>>>>>> help?
>>>>>>
>>>>>> PS: Does anyone want to work on
>>>>>> https://issues.apache.org/jira/browse/FINERACT-1270? That's such a
>>>>>> mess...
>>>>>>
>>>>>> Regards,
>>>>>>> Bharath
>>>>>>> Lead Implementation Analyst | Mifos Initiative
>>>>>>> Skype: live:cbharath4| Mobile: +91.7019635592
>>>>>>> http://mifos.org  <http://facebook.com/mifos>
>>>>>>> <http://www.twitter.com/mifos>
>>>>>>>
>>>>>>
>

Fwd: [jira] Subscription: Fineract Resolved Last 2 Weeks

[Michael Vorburger]

7 issues resolved since the last such email 2 weeks ago:

-- Forwarded message -
From: 
Date: Fri, Dec 4, 2020 at 2:03 AM
Subject: [jira] Subscription: Fineract Resolved Last 2 Weeks
To: 




Issue Subscription
Filter: Fineract Resolved Last 2 Weeks
<https://issues.apache.org/jira/issues/?filter=12349982> (7 issues)
Subscriber: vorburger
T Patch Info Key Summary Assignee Reporter P Status Resolution Created Updated
Due Development
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1070>
FINERACT-1070 <https://issues.apache.org/jira/browse/FINERACT-1070>

Email Service Configurations defaults to port 25 irrespective of Port
number specified <https://issues.apache.org/jira/browse/FINERACT-1070>
Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> Francis
Guchie
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=francisguchie>
[image:
Critical] Resolved Fixed 03/Jul/20 03/Dec/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1262>
FINERACT-1262 <https://issues.apache.org/jira/browse/FINERACT-1262>

Document production deployment SSL certificate configuration
<https://issues.apache.org/jira/browse/FINERACT-1262>
Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Major] Resolved Fixed 18/Nov/20 28/Nov/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1173>
FINERACT-1173 <https://issues.apache.org/jira/browse/FINERACT-1173>

Error Message in case of missing reporting implementation is confusing
<https://issues.apache.org/jira/browse/FINERACT-1173>
Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Major] Resolved Fixed 04/Oct/20 28/Nov/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1265>
FINERACT-1265 <https://issues.apache.org/jira/browse/FINERACT-1265>

ImageTest > getOriginalSize() FAILED expected: text/plain but was :
image/jpeg <https://issues.apache.org/jira/browse/FINERACT-1265>
Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Resolved Fixed 21/Nov/20 21/Nov/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1169>
FINERACT-1169 <https://issues.apache.org/jira/browse/FINERACT-1169>

fix for broken credit bureau loan-product mapping module
<https://issues.apache.org/jira/browse/FINERACT-1169>
Rahul Pawar
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rrpawar> Rahul
Pawar <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rrpawar>
[image:
Major] Resolved Fixed 01/Oct/20 02/Dec/20
[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-27>
FINERACT-27 <https://issues.apache.org/jira/browse/FINERACT-27>

Rescheduling Repayments that fall On Holidays, to a period of 30 days
<https://issues.apache.org/jira/browse/FINERACT-27>
Yemdjih Kaze Nasser
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kaze> Dayna
Harp
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dharp%40mifos.org>
[image:
Major] Resolved Fixed 18/Feb/16 28/Nov/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1258>
FINERACT-1258 <https://issues.apache.org/jira/browse/FINERACT-1258>

NPE at LoanAccountDomainServiceJpa.recalculateAccruals()
<https://issues.apache.org/jira/browse/FINERACT-1258>
Yemdjih Kaze Nasser
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kaze> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Closed Fixed 12/Nov/20 28/Nov/20
You may edit this subscription here
<https://issues.apache.org/jira/secure/EditSubscription!default.jspa?subId=23321=12349982>.


This message was sent by Atlassian Jira (v8.3.4#803005-sha1:1f96e09)
[image: Atlassian logo]

Re: Email Alerts

[Michael Vorburger]

I've left a comment on the related
https://issues.apache.org/jira/browse/FINERACT-1274.

I'm trying to understand why this request is not moving forward. It seems
like people are "hoping for" that some "volunteers" just "magically" do
this work "for them"? But the way it works in an open source project like
this one is basically just that someone who really wants this feature could
"sponsor" (pay for!) another party to do such a development. I was hoping
that such parties could be made to meet on this mailing list or through
JIRA issues and come to an agreement to get this kind of work done, but it
looks like that doesn't really work out like that...

On Tue, Dec 1, 2020 at 7:59 PM Javier Borkenztain  wrote:

> Hi, I've created this issue:
> https://issues.apache.org/jira/browse/FINERACT-1273 to kickstart the
> discussion
>
> [image: Logo] 
> *Javier Borkenztain* *| CEO*
> *e:* jav...@fiter.io
> *w:* fiter.io 
> *m:* +598 97980801
> [image: twitter icon]  [image: youtube icon]
>  [image:
> linkedin icon] 
>
> Sent via Superhuman 
>
>
> On Tue, Dec 01, 2020 at 12:14:53, Ed Cable  wrote:
>
>> Javier, this would be a wonderful way for your team at Fiterv to
>> contribute to the upstream community. If you're able to create a respective
>> ticket on jira, and continue discussion on this thread before opening up a
>> pull request. Look forward to this potential contribution.
>>
>> Ed
>>
>> On Mon, Mar 23, 2020, 09:37 Javier Borkenztain  wrote:
>>
>>> Hi Zayyad, we've built this functionality for some of our clients.
>>>
>>> We can support you on this if you need. Let me know.
>>>
>>> Javier
>>>
>>> On Thu, Mar 19, 2020 at 8:04 AM 
>>> wrote:
>>>
 Devs,



 I have a client request for email alerts to be sent to borrowers whose
 repayments are falling due.



 Mifos / Fineract as it is doesn’t have email field for clients and I
 suspect this will pose a challenge to set up email alerts.



 Is there anyone who has built something to send email alerts to clients?



 Kindly guide us on how we can achieve the same.



 Best Regards;

 *

 *Zayyad A. Said | Chairman & C.E.O*

 Cell No.: +254 716 615274 | Skype: *zsaid2011*

 Email: zay...@intrasofttechnologies.com

 Schedule Meetings: https://calendly.com/zayyadsaid



>>>
>>>
>>> --
>>> [image: Logo] 
>>> *Javier Borkenztain* *| CEO*
>>> *e:* jav...@fiter.io
>>> *w:* fiter.io 
>>> *m:* +598-94621188
>>> [image: twitter icon]  [image: youtube
>>> icon]  [image:
>>> linkedin icon] 
>>>
>>
>

Re: Fineract App Engine Flex Deployment issue

[Michael Vorburger]

Hello Tony,

I saw that you posted a similar question on the "Community App UI now with
CI/CD (and cui.fineract.dev removed)" email thread, so I'll attempt to
answer everything in this thread here instead:

> Do you have an app.yaml for the fineract.dev deployment on GAE Flex that
can be shared?

As per FAQ on https://www.fineract.dev: "We haven’t been able to figure out
how to explain the details of how this runs and make it an effective use of
your and our time." Sorry if that's (intentionally) a bit evasive... ;-)
But see below.

> I was also wondering if you use the dockerfile as is for the deployment
and how you set that up without using docker compose.

Yeah, exactly, I use the dockerfile as is. The Docker Compose isn't useful,
in this scenario. So I basically just build
https://github.com/apache/fineract/blob/develop/Dockerfile on Google Cloud
Build and push it to Google Container Registry (because AppEngine cannot
read from Docker Hub).

On Mon, Nov 23, 2020 at 8:53 PM Tony O  wrote:

> Hello Community,
> Anyone able to deploy fineract on Google App Engine flex  successfully?
> I am having a connection exception when fineract tries to make a
> connection to a Cloud Sql instance in the same VPC network.
>
> Error: Caused by: com.mysql.cj.jdbc.exceptions.CommunicationsException:
> Communications link failure
>
> 1. I set the JDBC parameters as environment variable in my app.yaml file :
>

The one you showed below looks pretty good, mine looks essentially like
that, so you must be close, but I did spot one thing:


> runtime: custom
> env: flex
>
> env_variables:
>   DRIVERCLASS_NAME: "com.mysql.jdbc.Driver"
>   PROTOCOL: "jdbc"
>   SUB_PROTOCOL: "mysql"
>   fineract_tenants_driver: "com.mysql.jdbc.Driver"
>   fineract_tenants_url: "jdbc:mysql://IP:3306/fineract_tenants"
>   fineract_tenants_uid: "root"
>

PLEASE don't EVER use default passwords... ;-)


>   fineract_tenants_pwd: "mysql"
>   FINERACT_DEFAULT_TENANTDB_HOSTNAME: ""
>

This seems wrong, no? Compare this to
https://github.com/apache/fineract/blob/develop/docker-compose.yml#L53.. it
must be the hostname of where you tenants DB is. How can it be empty? ;-)

Also I our docker-compose.yml example doesn't quote the YAML values, but
that shouldn't make any difference.


>   FINERACT_DEFAULT_TENANTDB_PORT: "3306"
>   FINERACT_DEFAULT_TENANTDB_UID: "root"
>

as above

  FINERACT_DEFAULT_TENANTDB_PWD: "IP"
>

erm... not IP, but some your well chosen super secret password here, yes?
;-)

2. I provide a simple Dockerfile - openjdk11
>

as above, this shouldn't actually be needed.


> FROM gcr.io/distroless/java:11 as fineract
>
> ADD fineract-provider.jar fineract-provider.jar
>
> ENTRYPOINT ["java","-jar","fineract-provider.jar"]
>
> ===
> Appreciate anyone helping to figure out why I am getting a connection
> issue.
>

Does this help?

Could I ask you a question: If with 1 click you could simply "rent" a
pre-configured dedicated private tenant on https://www.fineract.dev, or
another server like it, instead of having to figure all this out yourself,
would you use it?

Best,
M.
___
Michael Vorburger
http://www.vorburger.ch

Fwd: [jira] Subscription: Fineract Blockers

[Michael Vorburger]

If anyone reading this is interested in contributing but doesn't know
what/where, our list of open Blockers has a number of known problems that
would be great to address:


-- Forwarded message -
From: 
Date: Fri, Nov 20, 2020 at 2:02 AM
Subject: [jira] Subscription: Fineract Blockers
To: 




Issue Subscription
Filter: Fineract Blockers
<https://issues.apache.org/jira/issues/?filter=12349014> (17 issues)
Subscriber: vorburger
T Patch Info Key Summary Assignee Reporter P Status Resolution Created Updated
Due Development
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1086>
FINERACT-1086 <https://issues.apache.org/jira/browse/FINERACT-1086>

JpaOptimisticLockingFailureException at
LoanSchedularServiceImpl.recalculateInterest() - requires retry logic?
<https://issues.apache.org/jira/browse/FINERACT-1086>
*Unassigned* Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Open *Unresolved* 11/Jul/20 11/Jul/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1121>
FINERACT-1121 <https://issues.apache.org/jira/browse/FINERACT-1121>

NoSuchElementException at
AbstractLoanScheduleGenerator.checkIfFirstRepaymentDateisOnHolidayOrNonWorkingDay
<https://issues.apache.org/jira/browse/FINERACT-1121>
*Unassigned* Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Open *Unresolved* 20/Aug/20 20/Aug/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1085>
FINERACT-1085 <https://issues.apache.org/jira/browse/FINERACT-1085>

JournalEntryInvalidException: Journal entry cannot be made prior to last
account closing date for the branch at
org.apache.fineract.accounting.journalentry.service.AccountingProcessorHelper.checkForBranchClosures()
<https://issues.apache.org/jira/browse/FINERACT-1085>
*Unassigned* Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Open *Unresolved* 11/Jul/20 12/Sep/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1155>
FINERACT-1155 <https://issues.apache.org/jira/browse/FINERACT-1155>

NPE at AddressWritePlatformServiceImpl.addNewClientAddress()
<https://issues.apache.org/jira/browse/FINERACT-1155>
Manthan Surkar
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=manthan> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Open *Unresolved* 22/Sep/20 22/Sep/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1157>
FINERACT-1157 <https://issues.apache.org/jira/browse/FINERACT-1157>

UnsupportedOperationException at InteropServiceImpl
<https://issues.apache.org/jira/browse/FINERACT-1157>
*Unassigned* Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Open *Unresolved* 23/Sep/20 24/Sep/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-980>
FINERACT-980 <https://issues.apache.org/jira/browse/FINERACT-980>

bootRun broken due to FlywayDbUpgradeRequiredException: MySQL upgrade
required: MySQL 0.1 is outdated and no longer supported by Flyway. Flyway
currently supports MySQL 5.1 and newer.
<https://issues.apache.org/jira/browse/FINERACT-980>
Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] In Progress *Unresolved* 16/May/20 09/Oct/20
[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-982>
FINERACT-982 <https://issues.apache.org/jira/browse/FINERACT-982>

Completely ditch use of Drizzle JDBC Driver after all
<https://issues.apache.org/jira/browse/FINERACT-982>
Yemdjih Kaze Nasser
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kaze> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] In Progress *Unresolved* 16/May/20 11/Oct/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1221>
FINERACT-1221 <https://issues.apache.org/jira/browse/FINERACT-1221>

Fineract Client Java SDK API has broken methods
<https://issues.apache.org/jira/browse/FINERACT-1221>
*Unassigned* Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Open *Unresolved* 18/Oct/20 19/Oct/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1224>
FINERACT-1224 <https://issues.apache.org/jira/browse/FINERACT-1224>

NullPointerException at Base64$Encoder.encode() in ImagesApiResource
<https://issues.apache.org/jira/browse/FINERACT-1224>
Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> Michael
Vorb

Fwd: [jira] Subscription: Fineract Resolved Last 3 Weeks

[Michael Vorburger]

Hello, below is the usual list of 10 (!) issues resolved since my last such
email 3 weeks ago - keep it coming!


-- Forwarded message -
From: 
Date: Sat, Nov 21, 2020 at 11:48 AM
Subject: [jira] Subscription: Fineract Resolved Last 3 Weeks
To: 




Issue Subscription
Filter: Fineract Resolved Last 3 Weeks
<https://issues.apache.org/jira/issues/?filter=12349983> (10 issues)
Subscriber: vorburger
T Patch Info Key Summary Assignee Reporter P Status Resolution Created Updated
Due Development
[image: New Feature] <https://issues.apache.org/jira/browse/FINERACT-1209>
FINERACT-1209 <https://issues.apache.org/jira/browse/FINERACT-1209>

Integration Tests using new Swagger Client API ("Fineract SDK")
<https://issues.apache.org/jira/browse/FINERACT-1209>
Aleksandar Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Major] Resolved Fixed 17/Oct/20 12/Nov/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1250>
FINERACT-1250 <https://issues.apache.org/jira/browse/FINERACT-1250>

AuditIntegrationTest > auditShouldbeCreated() FAILED
org.opentest4j.AssertionFailedError: More than one audit created ==>
expected: <1> but was: <2>
<https://issues.apache.org/jira/browse/FINERACT-1250>
Aleksandar Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Major] Resolved Fixed 01/Nov/20 03/Nov/20
[image: Sub-task] <https://issues.apache.org/jira/browse/FINERACT-1191>
FINERACT-1191 <https://issues.apache.org/jira/browse/FINERACT-1191>

FINERACT-1171 <https://issues.apache.org/jira/browse/FINERACT-1171>
fineract-doc <https://issues.apache.org/jira/browse/FINERACT-1191>
Aleksandar Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Major] Resolved Implemented 09/Oct/20 03/Nov/20
[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-1241>
FINERACT-1241 <https://issues.apache.org/jira/browse/FINERACT-1241>

Elastic web hook <https://issues.apache.org/jira/browse/FINERACT-1241>
Manoj <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=fynmanoj>
Manoj <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=fynmanoj>
[image:
Minor] Resolved Fixed 24/Oct/20 12/Nov/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1247>
FINERACT-1247 <https://issues.apache.org/jira/browse/FINERACT-1247>

ImageTest failures <https://issues.apache.org/jira/browse/FINERACT-1247>
Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Major] Resolved Fixed 31/Oct/20 18/Nov/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1256>
FINERACT-1256 <https://issues.apache.org/jira/browse/FINERACT-1256>

Bulk Import Template generation should not fail for (office) names
containing hyphens and other characters invalid as Sheet Range Names
<https://issues.apache.org/jira/browse/FINERACT-1256>
Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Major] Resolved Fixed 07/Nov/20 12/Nov/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1255>
FINERACT-1255 <https://issues.apache.org/jira/browse/FINERACT-1255>

Staff Swagger declaration is wrong
<https://issues.apache.org/jira/browse/FINERACT-1255>
Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Major] Resolved Fixed 06/Nov/20 12/Nov/20
[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-1252>
FINERACT-1252 <https://issues.apache.org/jira/browse/FINERACT-1252>

Bump ancient OkHTTP v2.7.5 to current 4.x and Retrofit 1.9.0 to current
2.9.0 <https://issues.apache.org/jira/browse/FINERACT-1252>
Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Major] Resolved Fixed 01/Nov/20 07/Nov/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1220>
FINERACT-1220 <https://issues.apache.org/jira/browse/FINERACT-1220>

Client Java SDK must configure GSON to deserialize [,mm,dd] date format
returned by Fineract API
<https:/

Re: Fineract SSL Certificate Issue

[Michael Vorburger]

Hello Ben,

sorry it took a moment to be able to get back to you in this matter.

Re. "I have to explicitly visit the fineract server endpoint and select to
proceed to site before the page loads.", yes, that's documented e.g. on
https://github.com/openMF/community-app/#connecting-to-a-mifosx-platform-running-on-a-different-host.
To make local development easier, your browser has an option to permanently
accept Fineract's development self signed certificate.

Re. a real world production deployment, and how I handled the Cert issue on
https://www.fineract.dev, I'm contributing
https://github.com/apache/fineract/pull/1503/files with proposed
documentation about this, and hope that it helps to clarify this for you,
and others in the future.

Best,
M.
_______
Michael Vorburger
http://www.vorburger.ch

On Mon, Nov 2, 2020 at 8:42 PM Ben Njoka  wrote:

>
> Hi Michael,
>
>
> I deployed Fineract as an executable jar on a Google Cloud VM.
>
> java -jar fineract-provider.jar
> End Point: https://IP:8443/
>
> I also have an angular frontend served by a nginx web server listening on
> port 80 on the same VM - http://IP
> My frontend points to the Fineract API server at *https://IP
> <https://IP>: 8443/fineract-provider/api * defined in environment.prod.ts
>
> I can access my frontend at http://IP
> However, the page does not load due to Cert err. I have to explicitly visit 
> the
> fineract server endpoint and select to proceed to site before the page loads.
>
> Question:
> How did you handle the cert issue in your GCP deployment?
> I expect the browser to at least give me the option to
> proceed with warning with the self-signed cert
>
> Thanks,
> Ben.
>
> 
>

Re: RE: new column in table and new Table in database

[Michael Vorburger]

Mashood,

If you modify an Entity class, the new column won't automatically get added
to the database.

Instead, you need to provide a new Flyway migration SQL script, like all
the existing ones in
https://github.com/apache/fineract/tree/develop/fineract-provider/src/main/resources/sql/migrations/core_db.
Does that make sense?

Will you eventually be contributing your improvement to the project with a
pull request?

Best,
M.


On Thu, 12 Nov 2020, 13:35 Mashood hassan,  wrote:

> any help will be greatly appreciated. meanwhile, I search more about it.
>
> On Thu, Nov 12, 2020 at 5:33 PM Mashood hassan 
> wrote:
>
>> ok ok, manually I can create a column and table too, column not found
>> error occurs when i create manually column in table and try to get the
>> "/founds" through the api
>>
>> On Thu, Nov 12, 2020 at 5:30 PM Saifudeen Khan 
>> wrote:
>>
>>> I did not do it via program though, I did it manually. What I can help
>>> you is to figure out why tables are not created manually as well
>>>
>>>
>>>
>>> *From:* Mashood hassan 
>>> *Sent:* 12 November 2020 17:58
>>> *To:* dev@fineract.apache.org
>>> *Subject:* Re: RE: new column in table and new Table in database
>>>
>>>
>>>
>>> CAUTION: This email originated from outside of the organization. Do not
>>> click links or open attachments unless you recognize the sender and know
>>> the content is safe.
>>>
>>>
>>>
>>> I am new with spring stuff. but I created a separate spring hibernate
>>> project and was able to modify table in memory database
>>>
>>>
>>>
>>> On Thu, Nov 12, 2020 at 5:24 PM Mashood hassan 
>>> wrote:
>>>
>>> maybe I am missing something in the code. can you give me a little time
>>> we can connect on TeamViewer you can check? this will be a great help for
>>> me.
>>>
>>>
>>>
>>> On Thu, Nov 12, 2020 at 5:20 PM Saifudeen Khan 
>>> wrote:
>>>
>>> Strange. We had some usecases where we wanted frequencies of repayment
>>> for both principal and interest is different and able to modify the tables
>>> successfully
>>>
>>> -Original Message-
>>> From: Mashood hassan 
>>> Sent: 12 November 2020 17:46
>>> To: dev@fineract.apache.org
>>> Subject: Re: RE: new column in table and new Table in database
>>>
>>> CAUTION: This email originated from outside of the organization. Do not
>>> click links or open attachments unless you recognize the sender and know
>>> the content is safe.
>>>
>>>
>>> and now i have also created the column MySQL default fineract-database
>>> now i am getting the same error Caused by: java.sql.SQLException: No such
>>> column: source_of_fund
>>>
>>>
>>> On 2020/11/12 12:02:57, Mashood hassan  wrote:
>>> > yes, I did this one approach let me confirm this one I will tell you
>>> just a mint.
>>> > On 2020/11/12 11:53:34, Saifudeen Khan  wrote:
>>> > > Did you try creating the column in MySQL manually?
>>> > >
>>> > > -Original Message-
>>> > > From: Mashood hassan 
>>> > > Sent: 12 November 2020 17:21
>>> > > To: dev@fineract.apache.org
>>> > > Subject: new column in table and new Table in database
>>> > >
>>> > > CAUTION: This email originated from outside of the organization. Do
>>> not click links or open attachments unless you recognize the sender and
>>> know the content is safe.
>>> > >
>>> > >
>>> > >  I am working on Fineract. The issue I am facing is when I change in
>>> m_fund Entity class to add a new column it compiles without error but it
>>> does not create new column in MySQL database. one more strange thing which
>>> I came to know that is when I try to monitor the SQL logs by enabling it in
>>> the application.properties when it starts compiling it remove my lines
>>> which enables the SQL logs it feels like it is rewriting my changes. I am
>>> stuck at this stage I want to work on this project. Is there anyway u can
>>> help me on this? just guide me a little so that I continue my exploration
>>> on this cool project.
>>> > >
>>> > > 1: what do I want to do?
>>> > >  I want to add a new column and make new tables in fineract
>>> MySQL default.
>>> > > 2: what is the issue?
>>> > >  A new column is not visible in MySQL "m_fund" table even there
>>> is not an error
>>> > >  When I hit API /funds it says you don't have a "funds_type"
>>> column in the database. this is after when I make Column in Entity class
>>> using @Column and private String...
>>> > >
>>> > > Thank you
>>> > >
>>> > >
>>> > >
>>> > >
>>> > >
>>> > > Disclaimer: "The contents of this e-mail and any attachments
>>> enclosed therein are intended solely for the addressee(s) and may contain
>>> confidential and/or privileged information. It may also be the sole
>>> intellectual and proprietary resource of Zuci Systems and therefore may be
>>> legally protected from disclosure. If you are not the intended recipient of
>>> this message, or if this message has been addressed to you by inadvertence,
>>> kindly alert the sender by email and then follow with its deletion. If you
>>> are not the intended recipient, you are 

Re: Community App UI now with CI/CD (and cui.fineract.dev removed)

[Michael Vorburger]

On Wed, Nov 4, 2020 at 1:20 AM Michael Vorburger  wrote:

> Hello everyone,
>
> just wanted to let you all know that with
> https://github.com/openMF/community-app/issues/3309 implemented, you can
> now use
> https://openmf.github.io/community-app?baseApiUrl=https://demo.fineract.dev=default.
> This will now always have the latest community-app code.
>
> Best,
> M.
>
> PS: I've also completely removed cui.fineract.dev, as it's no longer
> needed now. (That's JUST the UI; the demo.fineract.dev still runs on
> https://www.fineract.dev, obviously.)
>
> PPS: As soon as https://github.com/openMF/web-app/pull/1256 is merged,
> and/or someone steps up to implement
> https://github.com/openMF/web-app/issues/786, I'd like to do the same and
> replace wui.fineract.dev as well.
>

FYI thanks to Abhay Chawla having merged
https://github.com/openMF/web-app/pull/1256, the https://www.fineract.dev
home page can now directly link to https://openmf.github.io/web-app/ (which
now uses demo.fineract.dev instead of mifos.io), and wui.fineract.dev
(which was outdated) is completely removed, as it's also no longer needed
now. (That's JUST the UI; the demo.fineract.dev still runs on
https://www.fineract.dev from the code on
https://github.com/apache/fineract/, obviously.)

Community App UI now with CI/CD (and cui.fineract.dev removed)

[Michael Vorburger]

Hello everyone,

just wanted to let you all know that with
https://github.com/openMF/community-app/issues/3309 implemented, you can
now use
https://openmf.github.io/community-app?baseApiUrl=https://demo.fineract.dev=default.
This will now always have the latest community-app code.

Best,
M.

PS: I've also completely removed cui.fineract.dev, as it's no longer needed
now. (That's JUST the UI; the demo.fineract.dev still runs on
https://www.fineract.dev, obviously.)

PPS: As soon as https://github.com/openMF/web-app/pull/1256 is merged,
and/or someone steps up to implement
https://github.com/openMF/web-app/issues/786, I'd like to do the same and
replace wui.fineract.dev as well.

___
Michael Vorburger
http://www.vorburger.ch

Reverting merged PR which broke the build

[Michael Vorburger]

Dear Community,

I've taken the typically somewhat unusual step and in the interest of
unblocking the community made the decision to REVERT the Merge of a PR
which broke the build of the develop branch for PRs from everyone. Details
available in https://issues.apache.org/jira/browse/FINERACT-1241.

Hope this process makes sense to all of you as the natural and right thing
to do in such situations. (As far as I remember, this is the first time
that we had to do this.) This is NOT a reflection on that contribution, and
I sincerely hope this won't discourage interest from the involved parties
to re-contribute their reverted work in a new PR without the test failure,
and more in the future.

With the merge of https://github.com/apache/fineract/pull/1474, our develop
branch now builds green again. There were actually 2 other problems,
completely unrelated to FINERACT-1241 (so 3 problems in total causing build
failures); see https://issues.apache.org/jira/browse/FINERACT-1247 and
https://issues.apache.org/jira/browse/FINERACT-1248; I'll deal with
FINERACT-1247, but who can step up to fix FINERACT-1248?

M.
___
Michael Vorburger
http://www.vorburger.ch

Fwd: [jira] Subscription: Fineract Resolved Last Week

[Michael Vorburger]

Hello everyone, below is the list of the 6 JIRA issues that were fixed over
the last week - many thanks to Percy, Bharath Gowda, Aleks and ;) myself:


-- Forwarded message -
From: 
Date: Fri, Oct 30, 2020 at 2:02 AM
Subject: [jira] Subscription: Fineract Resolved Last Week
To: 




Issue Subscription
Filter: Fineract Resolved Last Week
<https://issues.apache.org/jira/issues/?filter=12349018> (6 issues)
Subscriber: vorburger
T Patch Info Key Summary Assignee Reporter P Status Resolution Created Updated
Due Development
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1231>
FINERACT-1231 <https://issues.apache.org/jira/browse/FINERACT-1231>

SDK Swagger Java Client generated utilities are broken and should be
removed from JAR <https://issues.apache.org/jira/browse/FINERACT-1231>
Aleksandar Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Resolved Fixed 20/Oct/20 23/Oct/20
[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-1165>
FINERACT-1165 <https://issues.apache.org/jira/browse/FINERACT-1165>

Savings Account Scalability Improvement
<https://issues.apache.org/jira/browse/FINERACT-1165>
bharath gowda
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=bgowda> bharath
gowda <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=bgowda>
[image:
Major] Resolved Fixed 29/Sep/20 23/Oct/20
[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-1218>
FINERACT-1218 <https://issues.apache.org/jira/browse/FINERACT-1218>

Missing Integration Test coverage for Document Management functionality
<https://issues.apache.org/jira/browse/FINERACT-1218>
Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Major] Resolved Fixed 18/Oct/20 27/Oct/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1242>
FINERACT-1242 <https://issues.apache.org/jira/browse/FINERACT-1242>

OfficeTest fails with java.time.format.DateTimeParseException: Text
'2020-10-25' could not be parsed: Unable to obtain LocalDateTime from
TemporalAccessor: {DayOfMonth=25, Year=2020},ISO resolved to 00:10 of type
java.time.format.Parsed
<https://issues.apache.org/jira/browse/FINERACT-1242>
Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Resolved Fixed 25/Oct/20 27/Oct/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1234>
FINERACT-1234 <https://issues.apache.org/jira/browse/FINERACT-1234>

Client Java SDK must configure GSON to serialize -mm-dd date format
<https://issues.apache.org/jira/browse/FINERACT-1234>
Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Major] Resolved Fixed 21/Oct/20 23/Oct/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-826>
FINERACT-826 <https://issues.apache.org/jira/browse/FINERACT-826>

Migrate to java.time from Joda API
<https://issues.apache.org/jira/browse/FINERACT-826>
Percy Ashu
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Percy%20Ashu>
Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Major] Resolved Fixed 12/Jan/20 26/Oct/20
You may edit this subscription here
<https://issues.apache.org/jira/secure/EditSubscription!default.jspa?subId=23124=12349018>.


This message was sent by Atlassian Jira (v8.3.4#803005-sha1:1f96e09)
[image: Atlassian logo]

Fwd: [jira] Subscription: Fineract Resolved Last Week

[Michael Vorburger]

Whoa - another 13 new issues resolved in just the 1 past week - see details
below! Incredible.

This brings the total resolved JIRAs since 1.4.0 for an upcoming 1.5.0 to 38
<https://issues.apache.org/jira/issues/?jql=project%20%3D%20FINERACT%20AND%20fixVersion%20%3D%201.5.0%20and%20status%3DResolved%20>.
The total number of new commits in develop for a future 1.5.0 since 1.4.0
is 173 <https://github.com/apache/fineract/compare/1.4.0...develop>.

PS: On a personal side note, I was able to make more time than usual this
week, but have (much) other work to go back to starting next week, so will
slow down again... ;-)


-- Forwarded message -
From: 
Date: Fri, Oct 23, 2020 at 3:00 AM
Subject: [jira] Subscription: Fineract Resolved Last Week
To: 




Issue Subscription
Filter: Fineract Resolved Last Week
<https://issues.apache.org/jira/issues/?filter=12349018> (13 issues)
Subscriber: vorburger
T Patch Info Key Summary Assignee Reporter P Status Resolution Created Updated
Due Development
[image: Sub-task] <https://issues.apache.org/jira/browse/FINERACT-1189>
FINERACT-1189 <https://issues.apache.org/jira/browse/FINERACT-1189>

FINERACT-1171 <https://issues.apache.org/jira/browse/FINERACT-1171> Swagger
fineract-client as separate module
<https://issues.apache.org/jira/browse/FINERACT-1189>
Aleksandar Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Major] Resolved Fixed 09/Oct/20 21/Oct/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1207>
FINERACT-1207 <https://issues.apache.org/jira/browse/FINERACT-1207>

Clean up fineract-provider/config/swagger following introduction of
fineract-client/ <https://issues.apache.org/jira/browse/FINERACT-1207>
Aleksandar Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Minor] Resolved Fixed 17/Oct/20 20/Oct/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1208>
FINERACT-1208 <https://issues.apache.org/jira/browse/FINERACT-1208>

-Werror javac compilerArg lost during move to multi modules
<https://issues.apache.org/jira/browse/FINERACT-1208>
Aleksandar Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Major] Resolved Fixed 17/Oct/20 18/Oct/20
[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-1203>
FINERACT-1203 <https://issues.apache.org/jira/browse/FINERACT-1203>

Make WAR non-executable to avoid confusion (because it's broken anyway)
<https://issues.apache.org/jira/browse/FINERACT-1203>
Aleksandar Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Minor] Resolved Fixed 14/Oct/20 17/Oct/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1100>
FINERACT-1100 <https://issues.apache.org/jira/browse/FINERACT-1100>

Swagger CodeGen WARN i.s.c.v.g.java.AbstractJavaCodegen - New (reserved
word) cannot be used as model name. Renamed to ModelNew
<https://issues.apache.org/jira/browse/FINERACT-1100>
Chinmay Kulkarni
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Grandolf49>
Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Minor] Resolved Fixed 02/Aug/20 17/Oct/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1036>
FINERACT-1036 <https://issues.apache.org/jira/browse/FINERACT-1036>

NullPointerException at DocumentManagementApiResource.createDocument()
<https://issues.apache.org/jira/browse/FINERACT-1036>
Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Resolved Fixed 14/Jun/20 22/Oct/20
[image: Sub-task] <https://issues.apache.org/jira/browse/FINERACT-1226>
FINERACT-1226 <https://issues.apache.org/jira/browse/FINERACT-1226>

FINERACT-1171 <https://issues.apache.org/jira/browse/FINERACT-1171> Travis
CI does not actually build new multi module project structure
<https://issues.apache.org/jira/browse/FINERACT-1226>
Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Major] Resolved Fixed 20/Oct/20 21/Oct/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1236>
FINERACT-1236 <https://issues.apache.org/jira/b

How to create demo data? (FINERACT-1238)

[Michael Vorburger]

Hello everyone,

How do you all think we could best bulk create some demo data e.g. on
https://www.fineract.dev, but more generally through some.. thing re-usable
that anyone interested in the project can easily use locally or on their
own servers as well?

https://issues.apache.org/jira/browse/FINERACT-1238 has some thoughts -
please chime in there, or here.

Apart from the technical "how" discussion, do people reading this have
input on WHAT "demo data" would be useful to see? I guess whatever
technical solution we come up with should... what, like create:

* O offices
* U users
* C clients as the users
* S saving accounts per client
* L loan accounts per client

Would this be a reasonable starting point?

Tx,
M.
_______
Michael Vorburger
http://www.vorburger.ch

Re: Finereract Customization

[Michael Vorburger]

gProcessServiceImpl.java:201: error:
> cannot find
>  symbol
> final FineractPlatformTenantConnection tenantConnection =
> tenant.get
> Connection();
>   ^
>   symbol:   class FineractPlatformTenantConnection
>   location: class PentahoReportingProcessServiceImpl
> 24 errors
>
> > Task :compileJava FAILED
>
> FAILURE: Build failed with an exception.
>
> * What went wrong:
> Execution failed for task ':compileJava'.
> > Compilation failed; see the compiler error output for details.
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug
> option to get more log output. Run with --scan to get full insights.
>
> * Get more help at https://help.gradle.org
>
> BUILD FAILED in 1m 30s
> 1 actionable task: 1 executed
> C:\Users\gelila\fineract-pentaho>
>
> Regards
> Tesfahiwet Truneh
>
> On Wed, 21 Oct 2020 at 10:18, Michael Vorburger  wrote:
>
>> Tesfahiwet,
>>
>> Please raise bug reports with details about what exactly is not working
>> for you on https://github.com/vorburger/fineract-pentaho/issues.
>>
>> That project is still new, and will likely still evolve.
>>
>> M.
>>
>>
>> On Wed, 21 Oct 2020, 09:00 Tesfahiwet Truneh, 
>> wrote:
>>
>>> Hi
>>> can anyone help me on how to build a fineract with the pentaho report
>>> included?  https://github.com/vorburger/fineract-pentaho is not working
>>> for me.
>>>
>>> Regards
>>> Tesfahiwet Truneh
>>>
>>> On Mon, 12 Oct 2020 at 17:08, airsay longcon 
>>> wrote:
>>>
>>>> For Pentaho reports to work, some customisation to the Fineract code
>>>> needs to be done. Due to licensing issues, Fineract cannot support pentaho
>>>> reporting out of the box
>>>>
>>>> On Mon, 12 Oct 2020 at 06:48, ጓይላና Tube  wrote:
>>>>
>>>>> Hi.
>>>>> Only Pentaho Reports are not working? table reports are working fine!
>>>>> any help?
>>>>>
>>>>> Regards
>>>>> Tesfahiwet
>>>>>
>>>>> On Mon, 12 Oct 2020 at 00:50, Airsay Longcon 
>>>>> wrote:
>>>>>
>>>>>> Outreach reports? Or pentaho reports? Pentaho reports don't work with
>>>>>> Fineract out of the box
>>>>>>
>>>>>> On 12 Oct 2020, at 00:12, ጓይላና Tube  wrote:
>>>>>>
>>>>>> 
>>>>>> Hello, I have a problem with the creation of a new report. in fact
>>>>>> when I create the report and I execute it there is no result. Has anyone
>>>>>> come across this problem before? I'm using the latest fineract.
>>>>>>
>>>>>> Regards
>>>>>> Tesfahiwet
>>>>>>
>>>>>> On Sun, 11 Oct 2020 at 16:34, Michael Vorburger 
>>>>>> wrote:
>>>>>>
>>>>>>> On Fri, 9 Oct 2020, 21:30 Airsay Longcon, 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Michael,
>>>>>>>> Great to read your detailed response on this. Regarding your advice
>>>>>>>> "And code!", some of us have very basic Java programming skill. How 
>>>>>>>> would
>>>>>>>> you advice one to rapidly improve Java coding ability. I learnt coding 
>>>>>>>> in
>>>>>>>> the days of Pascal and Basic(covers face). Any specific pointers to 
>>>>>>>> Java
>>>>>>>> training resource will be highly appreciated.
>>>>>>>>
>>>>>>>
>>>>>>> Web search for "learn Java". But contributing useful feedback and
>>>>>>> bug reports is also a great way to give back- you don't "have to" code,
>>>>>>> obviously; hope I didn't create that impression (apologies if I did!).
>>>>>>>
>>>>>>> I'm more of a functional person focusing on how best to get
>>>>>>>> Fineract/Mifos X as opposed to a technical person who is intimately
>>>>>>>> knowledgeable about the code-base
>>>>>>>>
>>>>>>>> Also are there any avenues to donate to the project to have
>>>>>>>> specific functionality built into Fineract.
>>>>>>>>
>>>

Re: Finereract Customization

[Michael Vorburger]

Tesfahiwet,

Please raise bug reports with details about what exactly is not working for
you on https://github.com/vorburger/fineract-pentaho/issues.

That project is still new, and will likely still evolve.

M.


On Wed, 21 Oct 2020, 09:00 Tesfahiwet Truneh,  wrote:

> Hi
> can anyone help me on how to build a fineract with the pentaho report
> included?  https://github.com/vorburger/fineract-pentaho is not working
> for me.
>
> Regards
> Tesfahiwet Truneh
>
> On Mon, 12 Oct 2020 at 17:08, airsay longcon 
> wrote:
>
>> For Pentaho reports to work, some customisation to the Fineract code
>> needs to be done. Due to licensing issues, Fineract cannot support pentaho
>> reporting out of the box
>>
>> On Mon, 12 Oct 2020 at 06:48, ጓይላና Tube  wrote:
>>
>>> Hi.
>>> Only Pentaho Reports are not working? table reports are working fine!
>>> any help?
>>>
>>> Regards
>>> Tesfahiwet
>>>
>>> On Mon, 12 Oct 2020 at 00:50, Airsay Longcon 
>>> wrote:
>>>
>>>> Outreach reports? Or pentaho reports? Pentaho reports don't work with
>>>> Fineract out of the box
>>>>
>>>> On 12 Oct 2020, at 00:12, ጓይላና Tube  wrote:
>>>>
>>>> 
>>>> Hello, I have a problem with the creation of a new report. in fact when
>>>> I create the report and I execute it there is no result. Has anyone come
>>>> across this problem before? I'm using the latest fineract.
>>>>
>>>> Regards
>>>> Tesfahiwet
>>>>
>>>> On Sun, 11 Oct 2020 at 16:34, Michael Vorburger 
>>>> wrote:
>>>>
>>>>> On Fri, 9 Oct 2020, 21:30 Airsay Longcon, 
>>>>> wrote:
>>>>>
>>>>>> Hi Michael,
>>>>>> Great to read your detailed response on this. Regarding your advice
>>>>>> "And code!", some of us have very basic Java programming skill. How would
>>>>>> you advice one to rapidly improve Java coding ability. I learnt coding in
>>>>>> the days of Pascal and Basic(covers face). Any specific pointers to Java
>>>>>> training resource will be highly appreciated.
>>>>>>
>>>>>
>>>>> Web search for "learn Java". But contributing useful feedback and bug
>>>>> reports is also a great way to give back- you don't "have to" code,
>>>>> obviously; hope I didn't create that impression (apologies if I did!).
>>>>>
>>>>> I'm more of a functional person focusing on how best to get
>>>>>> Fineract/Mifos X as opposed to a technical person who is intimately
>>>>>> knowledgeable about the code-base
>>>>>>
>>>>>> Also are there any avenues to donate to the project to have specific
>>>>>> functionality built into Fineract.
>>>>>>
>>>>>
>>>>> Now THAT is a VERY interesting question.. let's take this to a new
>>>>> email thread? I'll start it, with Subject "$€¥£₱"... ;-)
>>>>>
>>>>> On 9 Oct 2020, at 17:47, Michael Vorburger  wrote:
>>>>>>
>>>>>> 
>>>>>> Tube, we are very happy that you are up and running!
>>>>>>
>>>>>> There was a lot in this email thread .. ;-) In the future, it's
>>>>>> probably better to have shorter more specific emails about particular
>>>>>> subjects?
>>>>>>
>>>>>> There are 2-3 things here that seem worth it to briefly following up
>>>>>> on and sharing more about for everyone:
>>>>>>
>>>>>> A. The thing about "Waoh. I always thought it was part of the design
>>>>>> for Fineract to be connected to the Internet for it to start. I had run
>>>>>> into this problem during several tests at the height of the lockdown and
>>>>>> ripped out my hair trying to figure out what the problem was"... that 
>>>>>> just
>>>>>> got fixed!! By https://github.com/apache/fineract/pull/1375. Full
>>>>>> background in https://issues.apache.org/jira/browse/FINERACT-1180 =>
>>>>>> https://issues.apache.org/jira/browse/FINERACT-1181 =>
>>>>>> https://issues.apache.org/jira/browse/FINERACT-898
>>>>>>
>>>>>> B. The Drizzle related problem
>>>>>> https://issues.apache.or

Fineract SDK Java API Client (Swagger/OpenAPI Code Generator)

[Michael Vorburger]

Hello everyone,

Habemus a Fineract SDK Java API Client, see
https://github.com/apache/fineract/blob/develop/docs/developers/swagger/client.md


This is based on https://openapi-generator.tech. Is that cool, or what?

There's still more work to to be done, see
https://issues.apache.org/jira/issues/?jql=project%20%3D%20FINERACT%20AND%20component%20%3D%20SDK%20and%20resolution%20%3D%20Unresolved%20
- who wants to help with any of those?

Please use component "SDK" when filing issues in JIRA re. this brand new
Java API Client SDK.

Tx,
M.
___

Fwd: [jira] Subscription: Fineract Resolved Last Week

[Michael Vorburger]

Whoot whoot: 17 issues resolved during the last week, see below - what a
community!!


-- Forwarded message -
From: 
Date: Fri, Oct 16, 2020 at 3:01 AM
Subject: [jira] Subscription: Fineract Resolved Last Week
To: 




Issue Subscription
Filter: Fineract Resolved Last Week
<https://issues.apache.org/jira/issues/?filter=12349018> (17 issues)


Subscriber: vorburger
T Patch Info Key Summary Assignee Reporter P Status Resolution Created Updated
Due Development
[image: Sub-task] <https://issues.apache.org/jira/browse/FINERACT-1194>
FINERACT-1194 <https://issues.apache.org/jira/browse/FINERACT-1194>

FINERACT-1171 <https://issues.apache.org/jira/browse/FINERACT-1171> Move
Gradle wrapper to root folder
<https://issues.apache.org/jira/browse/FINERACT-1194>
Aleksandar Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> Aleksandar
Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> [image:
Major] Resolved Fixed 11/Oct/20 11/Oct/20

[image: Sub-task] <https://issues.apache.org/jira/browse/FINERACT-1188>
FINERACT-1188 <https://issues.apache.org/jira/browse/FINERACT-1188>

FINERACT-1171 <https://issues.apache.org/jira/browse/FINERACT-1171> README
and other files are not covered by Spotless
<https://issues.apache.org/jira/browse/FINERACT-1188>
Aleksandar Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Major] Resolved Implemented 09/Oct/20 14/Oct/20

[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-1178>
FINERACT-1178 <https://issues.apache.org/jira/browse/FINERACT-1178>

Allow usage of SQL connection parameters
<https://issues.apache.org/jira/browse/FINERACT-1178>
Cedric Khin
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Sugiuro> Cedric
Khin <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Sugiuro>
[image:
Minor] Resolved Fixed 05/Oct/20 13/Oct/20

[image: New Feature] <https://issues.apache.org/jira/browse/FINERACT-556>
FINERACT-556 <https://issues.apache.org/jira/browse/FINERACT-556>

Email Campaign <https://issues.apache.org/jira/browse/FINERACT-556>
Ippez Robert
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ippezrobert> Ippez
Roberts <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Ippez>
[image:
Major] Resolved Fixed 14/Nov/17 13/Oct/20

[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1199>
FINERACT-1199 <https://issues.apache.org/jira/browse/FINERACT-1199>

Jersey (JAX RS implementation) & Tomcat logging needs to be configured to
use slf4j instead of JUL
<https://issues.apache.org/jira/browse/FINERACT-1199>
Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Major] Resolved Fixed 11/Oct/20 13/Oct/20

[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-1078>
FINERACT-1078 <https://issues.apache.org/jira/browse/FINERACT-1078>

Make spring logs colorful
<https://issues.apache.org/jira/browse/FINERACT-1078>
Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> Yemdjih
Kaze Nasser
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kaze> [image:
Minor] Resolved Fixed 05/Jul/20 13/Oct/20

[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1195>
FINERACT-1195 <https://issues.apache.org/jira/browse/FINERACT-1195>

podman build is broken <https://issues.apache.org/jira/browse/FINERACT-1195>
Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Resolved Fixed 11/Oct/20 13/Oct/20

[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1175>
FINERACT-1175 <https://issues.apache.org/jira/browse/FINERACT-1175>

Fix spm.repository / spm.domain JPA bug (?), and simplify appContext.xml
<https://issues.apache.org/jira/browse/FINERACT-1175>
Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Major] Resolved Fixed 05/Oct/20 11/Oct/20

[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1192>
FINERACT-1192 <https://issues.apache.org/jira/browse/FINERACT-1192>

Renovate does not update spring-framework-bom dependencyManagement
<https://issues.apache.org/jira/browse/FINERACT-1192>
Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> Michae

Re: Finereract Customization

[Michael Vorburger]

Re. Pentaho, please note https://github.com/vorburger/fineract-pentaho/ ...
it's brand new, and still needs testing by more people. You are very
welcome to try it out and provide feedback, ideally best by commenting on
https://issues.apache.org/jira/browse/FINERACT-1127 instead of on this
email thread.

PS: There was a lot in this email thread .. ;-) It's probably easier to
follow to have shorter more specific emails about particular new topics.

On Mon, 12 Oct 2020, 23:53 James Dailey,  wrote:

> Some of these questions are addressed in the documentation and FAQ.
> Please read
> https://cwiki.apache.org/confluence/display/FINERACT/Getting+Started+Docs
> and
> https://cwiki.apache.org/confluence/display/FINERACT/FAQ
>
>
>
> On Mon, Oct 12, 2020 at 9:08 AM airsay longcon 
> wrote:
>
>> For Pentaho reports to work, some customisation to the Fineract code
>> needs to be done. Due to licensing issues, Fineract cannot support pentaho
>> reporting out of the box
>>
>> On Mon, 12 Oct 2020 at 06:48, ጓይላና Tube  wrote:
>>
>>> Hi.
>>> Only Pentaho Reports are not working? table reports are working fine!
>>> any help?
>>>
>>> Regards
>>> Tesfahiwet
>>>
>>> On Mon, 12 Oct 2020 at 00:50, Airsay Longcon 
>>> wrote:
>>>
>>>> Outreach reports? Or pentaho reports? Pentaho reports don't work with
>>>> Fineract out of the box
>>>>
>>>> On 12 Oct 2020, at 00:12, ጓይላና Tube  wrote:
>>>>
>>>> 
>>>> Hello, I have a problem with the creation of a new report. in fact when
>>>> I create the report and I execute it there is no result. Has anyone come
>>>> across this problem before? I'm using the latest fineract.
>>>>
>>>> Regards
>>>> Tesfahiwet
>>>>
>>>> On Sun, 11 Oct 2020 at 16:34, Michael Vorburger 
>>>> wrote:
>>>>
>>>>> On Fri, 9 Oct 2020, 21:30 Airsay Longcon, 
>>>>> wrote:
>>>>>
>>>>>> Hi Michael,
>>>>>> Great to read your detailed response on this. Regarding your advice
>>>>>> "And code!", some of us have very basic Java programming skill. How would
>>>>>> you advice one to rapidly improve Java coding ability. I learnt coding in
>>>>>> the days of Pascal and Basic(covers face). Any specific pointers to Java
>>>>>> training resource will be highly appreciated.
>>>>>>
>>>>>
>>>>> Web search for "learn Java". But contributing useful feedback and bug
>>>>> reports is also a great way to give back- you don't "have to" code,
>>>>> obviously; hope I didn't create that impression (apologies if I did!).
>>>>>
>>>>> I'm more of a functional person focusing on how best to get
>>>>>> Fineract/Mifos X as opposed to a technical person who is intimately
>>>>>> knowledgeable about the code-base
>>>>>>
>>>>>> Also are there any avenues to donate to the project to have specific
>>>>>> functionality built into Fineract.
>>>>>>
>>>>>
>>>>> Now THAT is a VERY interesting question.. let's take this to a new
>>>>> email thread? I'll start it, with Subject "$€¥£₱"... ;-)
>>>>>
>>>>> On 9 Oct 2020, at 17:47, Michael Vorburger  wrote:
>>>>>>
>>>>>> 
>>>>>> Tube, we are very happy that you are up and running!
>>>>>>
>>>>>> There was a lot in this email thread .. ;-) In the future, it's
>>>>>> probably better to have shorter more specific emails about particular
>>>>>> subjects?
>>>>>>
>>>>>> There are 2-3 things here that seem worth it to briefly following up
>>>>>> on and sharing more about for everyone:
>>>>>>
>>>>>> A. The thing about "Waoh. I always thought it was part of the design
>>>>>> for Fineract to be connected to the Internet for it to start. I had run
>>>>>> into this problem during several tests at the height of the lockdown and
>>>>>> ripped out my hair trying to figure out what the problem was"... that 
>>>>>> just
>>>>>> got fixed!! By https://github.com/apache/fineract/pull/1375. Full
>>>>>> background in https://issues.apache.org/jira/browse/FINERACT-1180 =>
>>>>>

Re: $€¥£₱ - AKA donate to have specific functionality built?

[Michael Vorburger]

On Sun, Oct 11, 2020 at 5:53 PM Aleksandar Vidakovic <
chee...@monkeysintown.com> wrote:

> :+1: for the "Recommended Implementation Partners"... informally I think
> some people know these companies already, but it's a great idea to make
> this more visible.
>

BTW I was specifically thinking not ONLY of "these companies" but.. anyone
interested. Other users? Students? Why not!


On Sun, Oct 11, 2020 at 5:34 PM Michael Vorburger  wrote:
>
>> Hello Airsay & everyone,
>>
>> Airsay raised the following interesting question on the "Fineract
>> Customization" email thread, which to me seems worth discussing on a fresh
>> new email thread here:
>>
>> "Are there any avenues to donate to the project to have specific
>> functionality built into Fineract?"
>>
>> So, you CAN donate to the ASF at https://donate.apache.org, but this
>> ("just") contributes to the capex & opex costs of e.g.the Apache Software
>> Foundation (ASF) running issues.apache.org etc. for all projects.
>>
>> You CANNOT donate directly to our Apache Fineract project, and that's
>> perhaps a Good Thing and a Feature, not a Bug? ;-) It would be complicated
>> to determine where such money would go (IMHO).
>>
>> You COULD certainly just donate to specific individuals; e.g. I
>> personally set up https://github.com/sponsors/vorburger once.. :-)
>>
>> BUT I suspect that you may really be asking something else... what you
>> possibly are really getting at here is "I have problem XYZ or feature
>> request ABC, and am looking for someone to implement that for me, and am
>> willing to pay any interested party real money to do so" - am I right in
>> assuming that may at least partially be the real question that you were
>> asking?
>>
>> As far as I know, there absolutely are parties possibly interested in
>> working with folks such as you like this  (for full disclosure: I
>> personally am NOT one of them). But perhaps it's not so obvious to you how
>> to connect with such parties? I believe we all together as the project
>> community could perhaps do better at enabling this. A while ago we
>> discussed some ideas about creating some sort of magical sophisticated
>> "matchmaking marketplace" site for such requests. We haven't really
>> progressed on this, but... perhaps this really isn't that complicated? I
>> have a simple suggestion for you, and anyone else interested:
>>
>> If you need something done which you don't have the know how for
>> implementing yourself, and don't want to wait for a volunteer to possibly
>> look into some day, then first create a JIRA issue describing whatever it
>> is - as always. Then send a short email to this developer mailing list
>> sounding something like this: Subject: "$€¥£₱ for FINERACT-123", Body:
>> "Hello, we need FINERACT-123, and are willing to pay a mutually agreed upon
>> fee we'll privately settle on first to anyone interested who is able to
>> fully implement that to our specification when a Pull Request for the
>> requested functionality was made available and merged into the develop
>> branch of Fineract. Please direct reply offlist to me with any questions
>> and your proposed quotes for implementing issue FINERACT-123."
>>
>> BTW if I were you, I would fairly strongly feel that it is in both YOUR
>> and this community's interest to have any such work done "upstream first",
>> on https://github.com/apache/fineract. To you, it makes it easier to
>> upgrade to new releases. To us, it helps move a common unified code base
>> with new features and bug fixes forward. If it's functionality that someone
>> implements for you on a "private fork" that they are offering you, then
>> discussing that, IMHO, should not happen on this public mailing list at
>> all. We do understand that sometimes customization requests require changes
>> to existing code, but believe that it's possible to combine "upstream
>> first" and "local customizations" through modularity; there is currently
>> new energy on exploring this (NB FINERACT-1127 & FINERACT-1171) - more
>> about that separately later.
>>
>> Maybe you'll get 0 replies to such an email. But IMHO it's worth giving
>> that a try and see what you get... I'm (very) curious myself! It's IMHO
>> totally OK for follow-up discussions to be held privately. We the community
>> would simply see JIRAs being self assigned, pull requests being raised,
>> reviewed and merged. Money may have flown to Make It So - there's not

$€¥£₱ - AKA donate to have specific functionality built?

[Michael Vorburger]

Hello Airsay & everyone,

Airsay raised the following interesting question on the "Fineract
Customization" email thread, which to me seems worth discussing on a fresh
new email thread here:

"Are there any avenues to donate to the project to have specific
functionality built into Fineract?"

So, you CAN donate to the ASF at https://donate.apache.org, but this
("just") contributes to the capex & opex costs of e.g.the Apache Software
Foundation (ASF) running issues.apache.org etc. for all projects.

You CANNOT donate directly to our Apache Fineract project, and that's
perhaps a Good Thing and a Feature, not a Bug? ;-) It would be complicated
to determine where such money would go (IMHO).

You COULD certainly just donate to specific individuals; e.g. I personally
set up https://github.com/sponsors/vorburger once.. :-)

BUT I suspect that you may really be asking something else... what you
possibly are really getting at here is "I have problem XYZ or feature
request ABC, and am looking for someone to implement that for me, and am
willing to pay any interested party real money to do so" - am I right in
assuming that may at least partially be the real question that you were
asking?

As far as I know, there absolutely are parties possibly interested in
working with folks such as you like this  (for full disclosure: I
personally am NOT one of them). But perhaps it's not so obvious to you how
to connect with such parties? I believe we all together as the project
community could perhaps do better at enabling this. A while ago we
discussed some ideas about creating some sort of magical sophisticated
"matchmaking marketplace" site for such requests. We haven't really
progressed on this, but... perhaps this really isn't that complicated? I
have a simple suggestion for you, and anyone else interested:

If you need something done which you don't have the know how for
implementing yourself, and don't want to wait for a volunteer to possibly
look into some day, then first create a JIRA issue describing whatever it
is - as always. Then send a short email to this developer mailing list
sounding something like this: Subject: "$€¥£₱ for FINERACT-123", Body:
"Hello, we need FINERACT-123, and are willing to pay a mutually agreed upon
fee we'll privately settle on first to anyone interested who is able to
fully implement that to our specification when a Pull Request for the
requested functionality was made available and merged into the develop
branch of Fineract. Please direct reply offlist to me with any questions
and your proposed quotes for implementing issue FINERACT-123."

BTW if I were you, I would fairly strongly feel that it is in both YOUR and
this community's interest to have any such work done "upstream first", on
https://github.com/apache/fineract. To you, it makes it easier to upgrade
to new releases. To us, it helps move a common unified code base with new
features and bug fixes forward. If it's functionality that someone
implements for you on a "private fork" that they are offering you, then
discussing that, IMHO, should not happen on this public mailing list at
all. We do understand that sometimes customization requests require changes
to existing code, but believe that it's possible to combine "upstream
first" and "local customizations" through modularity; there is currently
new energy on exploring this (NB FINERACT-1127 & FINERACT-1171) - more
about that separately later.

Maybe you'll get 0 replies to such an email. But IMHO it's worth giving
that a try and see what you get... I'm (very) curious myself! It's IMHO
totally OK for follow-up discussions to be held privately. We the community
would simply see JIRAs being self assigned, pull requests being raised,
reviewed and merged. Money may have flown to Make It So - there's nothing
wrong with that (at least to me personally), and that doesn't have to be
public on list.

If something like the model outlined here takes on and proves to work, then
the Apache Fineract community could eventually even start to maintain some
sort of list, in a simple MD doc on Git, about "Recommended Implementation
Partners" - based on publicly verifiable contribution track records (i.e.
merged PRs) by parties offering such services in reply to "$€¥£₱ for
FINERACT-123" email threads.

Further thoughts on this topic very much welcome on this public thread!

M.

Re: Finereract Customization

[Michael Vorburger]

On Fri, 9 Oct 2020, 21:30 Airsay Longcon,  wrote:

> Hi Michael,
> Great to read your detailed response on this. Regarding your advice "And
> code!", some of us have very basic Java programming skill. How would you
> advice one to rapidly improve Java coding ability. I learnt coding in the
> days of Pascal and Basic(covers face). Any specific pointers to Java
> training resource will be highly appreciated.
>

Web search for "learn Java". But contributing useful feedback and bug
reports is also a great way to give back- you don't "have to" code,
obviously; hope I didn't create that impression (apologies if I did!).

I'm more of a functional person focusing on how best to get Fineract/Mifos
> X as opposed to a technical person who is intimately knowledgeable about
> the code-base
>
> Also are there any avenues to donate to the project to have specific
> functionality built into Fineract.
>

Now THAT is a VERY interesting question.. let's take this to a new email
thread? I'll start it, with Subject "$€¥£₱"... ;-)

On 9 Oct 2020, at 17:47, Michael Vorburger  wrote:
>
> 
> Tube, we are very happy that you are up and running!
>
> There was a lot in this email thread .. ;-) In the future, it's probably
> better to have shorter more specific emails about particular subjects?
>
> There are 2-3 things here that seem worth it to briefly following up on
> and sharing more about for everyone:
>
> A. The thing about "Waoh. I always thought it was part of the design for
> Fineract to be connected to the Internet for it to start. I had run into
> this problem during several tests at the height of the lockdown and ripped
> out my hair trying to figure out what the problem was"... that just got
> fixed!! By https://github.com/apache/fineract/pull/1375. Full background
> in https://issues.apache.org/jira/browse/FINERACT-1180 =>
> https://issues.apache.org/jira/browse/FINERACT-1181 =>
> https://issues.apache.org/jira/browse/FINERACT-898
>
> B. The Drizzle related problem
> https://issues.apache.org/jira/browse/FINERACT-980 will be "solved" by
> https://github.com/apache/fineract/pull/1366 for
> https://issues.apache.org/jira/browse/FINERACT-982. It will likely also
> create some new confusion, but ultimately will be the lesser evil..
> sometimes we have to make trade offs, and this email thread re-illustrates
> that we need to make another trade off on this question than we had in the
> past.
>
> C. Having to rename the WAR seems to cause confusion. Please chime in on
> https://issues.apache.org/jira/browse/FINERACT-1187 if you think we
> should revert that.
>
> We've made real nice progress here. Together we are stronger. Keep asking
> questions as a way of actively contributing. And code!
>
> M.
> ___
> Michael Vorburger
> http://www.vorburger.ch
>
>
> On Thu, Oct 8, 2020 at 7:18 PM ጓይላና Tube  wrote:
>
>> Ohh i can't believe it. now all things are working perfectly. The above
>> error was was caused by the community app I was using.  But,
>>  https://github.com/openMF/community-app/pull/3179/commits solved my
>> issue.
>> Thank you Petri, Michael, Bharath & all of you guys.
>>
>>>

Fwd: [jira] Subscription: Fineract Resolved Last Week

[Michael Vorburger]

See below 3 closed JIRAs over the last week (and some PRs).

Keep innovating!  PS: Enough emails for today? ;-)


-- Forwarded message -
From: 
Date: Fri, Oct 9, 2020 at 3:01 AM
Subject: [jira] Subscription: Fineract Resolved Last Week
To: 




Issue Subscription
Filter: Fineract Resolved Last Week
<https://issues.apache.org/jira/issues/?filter=12349018> (3 issues)
Subscriber: vorburger
T Patch Info Key Summary Assignee Reporter P Status Resolution Created Updated
Due Development
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1172>
FINERACT-1172 <https://issues.apache.org/jira/browse/FINERACT-1172>

Upgrade Flyway from 6.5.7 -> 7.0.0 (latest)
<https://issues.apache.org/jira/browse/FINERACT-1172>
Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Major] Resolved Fixed 04/Oct/20 04/Oct/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1154>
FINERACT-1154 <https://issues.apache.org/jira/browse/FINERACT-1154>

Git branch strategy is wrong, use tags instead
<https://issues.apache.org/jira/browse/FINERACT-1154>
Petri Tuomola
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ptuomola> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Major] Resolved Fixed 22/Sep/20 07/Oct/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1179>
FINERACT-1179 <https://issues.apache.org/jira/browse/FINERACT-1179>

Docker build broken <https://issues.apache.org/jira/browse/FINERACT-1179>
*Unassigned* Eliott Bouvard
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ebouvard> [image:
Major] Resolved Fixed 05/Oct/20 05/Oct/20
You may edit this subscription here
<https://issues.apache.org/jira/secure/EditSubscription!default.jspa?subId=23124=12349018>.


This message was sent by Atlassian Jira (v8.3.4#803005-sha1:1f96e09)
[image: Atlassian logo]

New committer: Manthan Surkar

[Michael Vorburger]

Hi (again, sorry for filling your Inboxes!),

The Project Management Committee (PMC) for Apache Fineract has invited
Manthan Surkar to become a committer, and we are pleased to announce that
he has accepted. The full list of all current Fineract committers is
visible here: https://projects.apache.org/committee.html?fineract.

Manthan started working on Apache Fineract in March 2020 as a Google Summer
of Code student (GSoC), and has made a real difference in Fineract by
contributing to Checkstyle (amazing), related error handling and logging,
Spotless (so cool), the SqlBuilder (WIP), and Swagger (check it out on
https://www.youtube.com/watch?v=FlVd-0YAo6c!). He's coincidentally at
exactly 99 Pull Requests
<https://github.com/apache/fineract/pulls?q=author%3Athesmallstar+> so far
- push 1 more so that you make it into the 100s! ;-)

Please join me in welcoming Manthan Surkar as an Apache Fineract committer.

M.
___
Michael Vorburger
http://www.vorburger.ch

Re: Finereract Customization

[Michael Vorburger]

Tube, we are very happy that you are up and running!

There was a lot in this email thread .. ;-) In the future, it's probably
better to have shorter more specific emails about particular subjects?

There are 2-3 things here that seem worth it to briefly following up on and
sharing more about for everyone:

A. The thing about "Waoh. I always thought it was part of the design for
Fineract to be connected to the Internet for it to start. I had run into
this problem during several tests at the height of the lockdown and ripped
out my hair trying to figure out what the problem was"... that just got
fixed!! By https://github.com/apache/fineract/pull/1375. Full background in
https://issues.apache.org/jira/browse/FINERACT-1180 =>
https://issues.apache.org/jira/browse/FINERACT-1181 =>
https://issues.apache.org/jira/browse/FINERACT-898

B. The Drizzle related problem
https://issues.apache.org/jira/browse/FINERACT-980 will be "solved" by
https://github.com/apache/fineract/pull/1366 for
https://issues.apache.org/jira/browse/FINERACT-982. It will likely also
create some new confusion, but ultimately will be the lesser evil..
sometimes we have to make trade offs, and this email thread re-illustrates
that we need to make another trade off on this question than we had in the
past.

C. Having to rename the WAR seems to cause confusion. Please chime in on
https://issues.apache.org/jira/browse/FINERACT-1187 if you think we should
revert that.

We've made real nice progress here. Together we are stronger. Keep asking
questions as a way of actively contributing. And code!

M.
___
Michael Vorburger
http://www.vorburger.ch


On Thu, Oct 8, 2020 at 7:18 PM ጓይላና Tube  wrote:

> Ohh i can't believe it. now all things are working perfectly. The above
> error was was caused by the community app I was using.  But,
>  https://github.com/openMF/community-app/pull/3179/commits solved my
> issue.
> Thank you Petri, Michael, Bharath & all of you guys.
>
>>

No maintenance branches (FINERACT-1154)

[Michael Vorburger]

Hello everyone,

The Fineract git repo used to have many git branches. This was a little bit
confusing, and allowed people to raise pull requests against other branches
than develop.

We have therefore decided to "close" all open branches and make them simple
git tags (which still allow one to easily see "how the code was" e.g. back
in 1.3.0 and earlier). This better reflects the reality that the community
really only works on the develop branch in git.

Maintaining "Long Term Support" (AKA "LTS") by "back-porting" fixes can be
one of many ways e.g. for System Integrators to offer additional value, and
is common in some open source communities.

Of course, any committer is welcome to offer their time to maintain past
releases and "backport" select fixes and step up as release managers e.g.
for 1.4.x, but as far as I know, the currently active committers focus on a
linear release (so a 1.5.0 next), only.

More background discussion about this can be found in
https://issues.apache.org/jira/browse/FINERACT-1154.

Best,
M.
___
Michael Vorburger
http://www.vorburger.ch

Re: Success breeds interest, begets momentum, drives project

[Michael Vorburger]

Yeah, it was a great ApacheCon!

BTW Slides from Fineract track on
https://drive.google.com/drive/folders/17ahcInsVSu5R00BaJKfCs_wh2XnCtLh4

Our presentations will be uploaded to
https://www.youtube.com/theapachefoundation over the coming weeks.

On Fri, Oct 2, 2020 at 7:33 PM James Dailey  wrote:

> Hi -
>
> This week at ApacheCon @ home was terrific.  A big shout out goes to
> Javier for all of the work he did to organize the first ever Fineract
> track.  In some sense, the online version was probably a much better format
> for this group, especially for the first time.  I get the sense that we
> built some important momentum.
>
> The ApacheCon organizers will be rendering the videos and posting them to
> youtube in the coming days and weeks.  Once those are up, we should link to
> them... probably from the Blog section of our wiki.  @Javier Borkenztain
>  big thank you.
>
> The "Birds of a Feather" discussions at the end of each day...were some of
> the most useful discussions about the future directions and challenges
> facing the Software Integrators and builders of the fineract platform(s).
> The last day session lasted until after 2am in the morning for our friends
> in Europe and I think one person stayed on past 3am in India.  You all get
> the "night owl" award.
>
> A few JIRA tickets were created related to some priorities we identified
> and I hope others will chime in with either comments or new email threads
> that cover new specific topics.
>
>
> Modularize Fineract to allow something like e.g. the Pentaho integration
> to be built and run separately
> https://issues.apache.org/jira/browse/FINERACT-1127
>
>
> Automated Load Testing Scenarios and Tooling
> https://issues.apache.org/jira/browse/FINERACT-1170
>
>
> I think the interest shown by the community of developers and software
> integrators demonstrates a very positive progression.  As Micheal pointed
> out in his talk, we've had a lot of renewed interest in the past 12 months
> on the fineract1.x platform.  We also heard from some software integrators
> about the directions that they would like to see taken by the community on
> both Fineract1.x and Fineract-CN and we hope to see those projects get on
> the upstream.  We heard about the work around AI for All as it applies to
> the project and we got a taste of the solution set around payments
> integration with Mojaloop and the new efforts around authentication.  We
> also got to hear about the importance of the project to financial inclusion
> and the need for a broad digital public good around G2P (govt to person)
> transfer payments.
>
> I am sure others have their take-aways, mine is that Success breeds
> interest, begets momentum, drives project.  Wishing you a happy Friday and
> a good weekend, be well.
>
> @jdailey
>

Re: Finereract Customization

[Michael Vorburger]

https://www.google.com/search?q=this+version+of+the+Java+Runtime+only+recogni+zes+class+file+versions+up+to+52.0


On Fri, Oct 2, 2020 at 3:43 PM ጓይላና Tube  wrote:

> I wanted to generate a fineract jar file rather than war. and i have
> generated a jar file called *fineract-provider-unknown.jar. *But, when I
> wanted to Start it using java -jar
> build/libs/fineract-provider-unknown.jar  I got this error any
> help/suggestion?
>
> C:\Users\gelila\Downloads\Compressed\fineract-develop\fineract-develop>java
> -jar
>  build/libs/fineract-provider-unknown.jar
> Exception in thread "main" java.lang.UnsupportedClassVersionError:
> org/apache/fi
> neract/ServerApplication has been compiled by a more recent version of the
> Java
> Runtime (class file version 55.0), this version of the Java Runtime only
> recogni
> zes class file versions up to 52.0
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(Unknown Source)
> at java.security.SecureClassLoader.defineClass(Unknown Source)
> at java.net.URLClassLoader.defineClass(Unknown Source)
> at java.net.URLClassLoader.access$100(Unknown Source)
> at java.net.URLClassLoader$1.run(Unknown Source)
> at java.net.URLClassLoader$1.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(Unknown Source)
> at java.lang.ClassLoader.loadClass(Unknown Source)
> at
> org.springframework.boot.loader.LaunchedURLClassLoader.loadClass(Laun
> chedURLClassLoader.java:151)
> at java.lang.ClassLoader.loadClass(Unknown Source)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Unknown Source)
> at
> org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner
> .java:46)
> at
> org.springframework.boot.loader.Launcher.launch(Launcher.java:107)
> at
> org.springframework.boot.loader.Launcher.launch(Launcher.java:58)
> at
> org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:88)
>
> On Thu, 1 Oct 2020 at 18:38, Michael Vorburger  wrote:
>
>> On Thu, Oct 1, 2020 at 9:47 AM ጓይላና Tube  wrote:
>>
>>> hi.
>>>
>>>> fiinally. i have created the fineract war file using gradlew clean war
>>>>> command. the above problem was @ build.gradle line 208 & the
>>>>> error had been taken care of by the following PR
>>>>> https://github.com/apache/fineract/pull/1359. but,
>>>>
>>>> after creating the war file successfully and deploy into tomcat
>>> server.  i got the message "couldn't connect to server". any help? here is
>>> the log file.
>>>
>>
>> Unfortunately not, as no error message shown below, so difficult to help
>> here.
>>
>>
>>> Oct 01, 2020 8:29:19 AM org.apache.catalina.startup.HostConfig deployWAR
>>> INFO: Deployment of web application archive
>>> [C:\tomcat\webapps\fineract-provider-unknown.war] has finished in [64,902]
>>> ms
>>> Oct 01, 2020 8:29:19 AM org.apache.catalina.startup.HostConfig
>>> deployDirectory
>>> INFO: Deploying web application directory [C:\tomcat\webapps\docs]
>>> Oct 01, 2020 8:29:19 AM org.apache.catalina.startup.TldConfig execute
>>> INFO: At least one JAR was scanned for TLDs yet contained no TLDs.
>>> Enable debug logging for this logger for a complete list of JARs that were
>>> scanned but no TLDs were found in them. Skipping unneeded JARs during
>>> scanning can improve startup time and JSP compilation time.
>>> Oct 01, 2020 8:29:19 AM org.apache.catalina.startup.HostConfig
>>> deployDirectory
>>> INFO: Deployment of web application directory [C:\tomcat\webapps\docs]
>>> has finished in [249] ms
>>> Oct 01, 2020 8:29:19 AM org.apache.catalina.startup.HostConfig
>>> deployDirectory
>>> INFO: Deploying web application directory [C:\tomcat\webapps\examples]
>>> Oct 01, 2020 8:29:23 AM org.apache.catalina.startup.TldConfig execute
>>> INFO: At least one JAR was scanned for TLDs yet contained no TLDs.
>>> Enable debug logging for this logger for a complete list of JARs that were
>>> scanned but no TLDs were found in them. Skipping unneeded JARs during
>>> scanning can improve startup time and JSP compilation time.
>>> Oct 01, 2020 8:29:23 AM org.apache.catalina.startup.HostConfig
>>> deployDirectory
>>> INFO: Deployment of web application directory
>>> [C:\tomcat\webapps\examples] has fin

Re: Finereract Customization

[Michael Vorburger]

On Thu, Oct 1, 2020 at 9:47 AM ጓይላና Tube  wrote:

> hi.
>
>> fiinally. i have created the fineract war file using gradlew clean war
>>> command. the above problem was @ build.gradle line 208 & the
>>> error had been taken care of by the following PR
>>> https://github.com/apache/fineract/pull/1359. but,
>>
>> after creating the war file successfully and deploy into tomcat server.
> i got the message "couldn't connect to server". any help? here is the log
> file.
>

Unfortunately not, as no error message shown below, so difficult to help
here.


> Oct 01, 2020 8:29:19 AM org.apache.catalina.startup.HostConfig deployWAR
> INFO: Deployment of web application archive
> [C:\tomcat\webapps\fineract-provider-unknown.war] has finished in [64,902]
> ms
> Oct 01, 2020 8:29:19 AM org.apache.catalina.startup.HostConfig
> deployDirectory
> INFO: Deploying web application directory [C:\tomcat\webapps\docs]
> Oct 01, 2020 8:29:19 AM org.apache.catalina.startup.TldConfig execute
> INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable
> debug logging for this logger for a complete list of JARs that were scanned
> but no TLDs were found in them. Skipping unneeded JARs during scanning can
> improve startup time and JSP compilation time.
> Oct 01, 2020 8:29:19 AM org.apache.catalina.startup.HostConfig
> deployDirectory
> INFO: Deployment of web application directory [C:\tomcat\webapps\docs] has
> finished in [249] ms
> Oct 01, 2020 8:29:19 AM org.apache.catalina.startup.HostConfig
> deployDirectory
> INFO: Deploying web application directory [C:\tomcat\webapps\examples]
> Oct 01, 2020 8:29:23 AM org.apache.catalina.startup.TldConfig execute
> INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable
> debug logging for this logger for a complete list of JARs that were scanned
> but no TLDs were found in them. Skipping unneeded JARs during scanning can
> improve startup time and JSP compilation time.
> Oct 01, 2020 8:29:23 AM org.apache.catalina.startup.HostConfig
> deployDirectory
> INFO: Deployment of web application directory [C:\tomcat\webapps\examples]
> has finished in [3,137] ms
> Oct 01, 2020 8:29:23 AM org.apache.catalina.startup.HostConfig
> deployDirectory
> INFO: Deploying web application directory [C:\tomcat\webapps\host-manager]
> Oct 01, 2020 8:29:23 AM org.apache.catalina.startup.TldConfig execute
> INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable
> debug logging for this logger for a complete list of JARs that were scanned
> but no TLDs were found in them. Skipping unneeded JARs during scanning can
> improve startup time and JSP compilation time.
> Oct 01, 2020 8:29:23 AM org.apache.catalina.startup.HostConfig
> deployDirectory
> INFO: Deployment of web application directory
> [C:\tomcat\webapps\host-manager] has finished in [242] ms
> Oct 01, 2020 8:29:23 AM org.apache.catalina.startup.HostConfig
> deployDirectory
> INFO: Deploying web application directory [C:\tomcat\webapps\manager]
> Oct 01, 2020 8:29:23 AM org.apache.catalina.startup.TldConfig execute
> INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable
> debug logging for this logger for a complete list of JARs that were scanned
> but no TLDs were found in them. Skipping unneeded JARs during scanning can
> improve startup time and JSP compilation time.
> Oct 01, 2020 8:29:23 AM org.apache.catalina.startup.HostConfig
> deployDirectory
> INFO: Deployment of web application directory [C:\tomcat\webapps\manager]
> has finished in [187] ms
> Oct 01, 2020 8:29:23 AM org.apache.catalina.startup.HostConfig
> deployDirectory
> INFO: Deploying web application directory [C:\tomcat\webapps\OLDROOT]
> Oct 01, 2020 8:29:23 AM org.apache.catalina.startup.TldConfig execute
> INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable
> debug logging for this logger for a complete list of JARs that were scanned
> but no TLDs were found in them. Skipping unneeded JARs during scanning can
> improve startup time and JSP compilation time.
> Oct 01, 2020 8:29:23 AM org.apache.catalina.startup.HostConfig
> deployDirectory
> INFO: Deployment of web application directory [C:\tomcat\webapps\OLDROOT]
> has finished in [137] ms
> Oct 01, 2020 8:29:23 AM org.apache.catalina.startup.HostConfig
> deployDirectory
> INFO: Deploying web application directory [C:\tomcat\webapps\ROOT]
> Oct 01, 2020 8:29:23 AM org.apache.catalina.startup.TldConfig execute
> INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable
> debug logging for this logger for a complete list of JARs that were scanned
> but no TLDs were found in them. Skipping unneeded JARs during scanning can
> improve startup time and JSP compilation time.
> Oct 01, 2020 8:29:23 AM org.apache.catalina.startup.HostConfig
> deployDirectory
> INFO: Deployment of web application directory [C:\tomcat\webapps\ROOT] has
> finished in [100] ms
> Oct 01, 2020 8:29:23 AM org.apache.coyote.AbstractProtocol start
> INFO: Starting 

Re: Finereract Customization

[Michael Vorburger]

Tube (?),

This is an interesting new problem that we are not yet aware of; thank you
for sharing it with us on the list (that's one good way of contributing and
helping the project).

Are you seeing this problem after a "git clone", or with sources that you
downloaded as a ZIP file? From where, how? I wonder
 if perhaps our build is broken when there is no .git/.

Or did you maybe use a Gradle that you have already installed ("gradle
bootJar"?) , instead of the Gradle Wrapper which you really have to use
("./gradlew bootJar"). Just to make sure, could you please share the EXACT
line you used to launch your local build? Like copy everything, starting
from the C:\ prompt and what EXACTLY you typed.

We should have a new open JIRA issue about it to track this problem, and
eventually the solution. Would you be able to create an issue for it for us?

Best,
M.

On Tue, 29 Sep 2020, 16:19 ጓይላና Tube,  wrote:

> hello
>  i want to create a fineract-provider jar/war file. When I run 퐠퐫퐚퐝퐥퐞퐰
> 퐜퐥퐞퐚퐧 퐛퐨퐨퐭퐉퐚퐫(jar)/퐠퐫퐚퐝퐥퐞퐰 퐜퐥퐞퐚퐧
> 퐛퐨퐨퐭퐖퐚퐫(war). I got this error. any help/fix?
>
> > Task :enhance
> Found no persistent property in
> "org.apache.fineract.infrastructure.dataqueries.
> domain.ReportParameter"
>
> > Task :prepareInputYaml FAILED
>
> FAILURE: Build failed with an exception.
>
> * Where:
> Build file
> 'C:\Users\gelila\Downloads\Compressed\fineract-develop\fineract-devel
> op\fineract-provider\build.gradle' line: 208
>
> * What went wrong:
> Execution failed for task ':prepareInputYaml'.
> > Cannot get property 'gitProps' on extra properties extension as it does
> not ex
> ist
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug
> option to get more log output. Run with --scan to get full insights.
>
> * Get more help at https://help.gradle.org
>
> Deprecated Gradle features were used in this build, making it incompatible
> with
> Gradle 7.0.
> Use '--warning-mode all' to show the individual deprecation warnings.
> See
> https://docs.gradle.org/6.6.1/userguide/command_line_interface.html#sec:comm
> and_line_warnings
>
> On Tue, 29 Sep 2020 at 13:11, ጓይላና Tube  wrote:
>
>> Okay Michael
>>
>> On Tue, 29 Sep 2020 at 12:33, Michael Vorburger 
>> wrote:
>>
>>> You need to run it under Java 11 instead of Java 8. The error message
>>> shown kind of says that ("Could not target platform... Java SE 11 using
>>> tool chain JDK 8 (1.8)"), but it's probably not clear enough?
>>>
>>> PS: When you post on public mailing lists, could you please always
>>> copy/paste text, instead of screenshots? That makes it easier for others to
>>> search for such errors, and find previous answers.
>>>
>>> On Tue, Sep 29, 2020 at 11:36 AM ጓይላና Tube 
>>> wrote:
>>>
>>>> Hello.
>>>> i want to create a fineract-provider jar file. When I
>>>> run 헴헿헮헱헹헲현 헰헹헲헮헻 헯헼헼혁헝헮헿. i got this error. any
>>>> help/suggestion?
>>>>
>>>>
>>>> [image: fail.jpg]
>>>>
>>>> On Tue, 29 Sep 2020 at 09:15, Mhretaab Brehe  wrote:
>>>>
>>>>> Wouldn't it be good to externalize (the database password particularly
>>>>> for fineract_tenants) to some property file or command line arguments so 
>>>>> as
>>>>> to avoid the password mysql?
>>>>> when you run the artifact java -jar fineract-provider.jar
>>>>> --db.password=your_finearact_tenants_password and some where within the
>>>>> code to use
>>>>> @value("${db.password}")String tenantsDbPassword;
>>>>>
>>>>> thanks
>>>>>
>>>>> On Mon, Sep 28, 2020 at 8:59 PM Michael Vorburger 
>>>>> wrote:
>>>>>
>>>>>> On Mon, Sep 28, 2020 at 7:42 PM Airsay Longcon <
>>>>>> airsaylong...@gmail.com> wrote:
>>>>>>
>>>>>>> Hi Michael,
>>>>>>> Thank you for the response. I understand that a straightforward java
>>>>>>> -jar would run the jar build. I guess my question was more about how to
>>>>>>> configure the other software like the Web-app and MySQL as I would like 
>>>>>>> to
>>>>>>> change the defaults such as the MySQL root password and port, the port
>>>>>>> which the community/web apps will run on and some other basic changes so
>>>>>>> that I don't have an environment that is a sitting duck for attacks
>>>&g

Re: Let's prepare for 1.5.0...

[Michael Vorburger]

Targeting a 3 months cycle sounds good to me, and longer term perhaps more
realistic than 2 months? So I would suggest 3, for now; possible reduction
to a 2 months window later, if our contributions suddenly explode... ;-)

More specifically, when exactly do you want to start counting? The date of
the last release email, 2 weeks ago? Or today-ish, that plus 3 months would
mean a 1.5.0 end of December, early January?

PS: I recommend that we we DO NOT have "code freezes", at all. That's such
a 90s concept... ;-) Instead, the RM will just create a (1.5.0) "release
branch" - exactly like we did for 1.4.0. That worked great. In parallel, we
should continue reviewing and merging into our "develop" branch. Always.
The show must go on. Releases should never "stop the world".


On Wed, 30 Sep 2020, 15:36 Awasum Yannick,  wrote:

> Michael, that is a good idea.
>
> Ed maybe we could do a release once every 2 or 3 months. A monthly release
> wont have alot of features based on the contribution rate. But doing it
> once every 2 or 3 months will have a sizeable list of bug fixes.
>
> What do you all think?
>
> On Wed, Sep 30, 2020, 14:06 Ed Cable  wrote:
>
>> Hi Michael,
>>
>> I think it would be good to aim for a time-boxed release cadence. That is
>> what we were aiming for before but I think given we had no release manager
>> and no steady review of PRs, the aim of bi-monthly releases was too
>> ambitious.
>>
>> What would you propose as a frequency of release cycle? - Quarterly?
>>
>> The processes and timelines previously proposed and implemented centered
>> around a 2 month period so I think a quarter would give more time to
>> effectively allow the community to prepare their contributions before code
>> freeze dates, etc.
>>
>> Ed
>>
>>
>>
>> On Wed, Sep 30, 2020 at 5:13 AM Bharath Gowda  wrote:
>>
>>> +1
>>> It's a great thought, codebase would become more stable with timely
>>> fixes and release. also, organizations can plan their work according to the
>>> release date.
>>>
>>>
>>> Regards,
>>> Bharath
>>> Lead Implementation Analyst | Mifos Initiative
>>> Skype: live:cbharath4| Mobile: +91.7019636073
>>> http://mifos.org  <http://facebook.com/mifos>
>>> <http://www.twitter.com/mifos>
>>>
>>>
>>> On Wed, Sep 30, 2020 at 5:29 PM Aleksandar Vidakovic <
>>> chee...@monkeysintown.com> wrote:
>>>
>>>> +1 ... like it.
>>>>
>>>> On Wed, Sep 30, 2020 at 1:09 PM Michael Vorburger 
>>>> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> I have an idea/proposal, for discussion/input:
>>>>>
>>>>> How crazy would it be to suggest a strictly time boxed release cadence
>>>>> for Fineract?
>>>>>
>>>>> So we would discuss and agree upon a DATE instead of SCOPE for 1.5.0.
>>>>>
>>>>> Best,
>>>>> M.
>>>>>
>>>>>
>>>>> On Wed, 30 Sep 2020, 08:54 Aleksandar Vidakovic, <
>>>>> chee...@monkeysintown.com> wrote:
>>>>>
>>>>>> Hi everyone,
>>>>>>
>>>>>> ... just wanted to start the discussion on what we want to include
>>>>>> for the next release. Let's see if we can establish a more regular 
>>>>>> release
>>>>>> cycle... looking at the current rate of contributions we should 
>>>>>> definitely
>>>>>> have enough material.
>>>>>>
>>>>>> Please chime in and either label existing or new Jira tickets for
>>>>>> version 1.5.0 or just send ideas and requests here on the mailing list.
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Aleks
>>>>>>
>>>>>
>>
>> --
>> *Ed Cable*
>> President/CEO, Mifos Initiative
>> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>>
>> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>> <http://facebook.com/mifos>  <http://www.twitter.com/mifos>
>>
>>

Re: Let's prepare for 1.5.0...

[Michael Vorburger]

Hello,

I have an idea/proposal, for discussion/input:

How crazy would it be to suggest a strictly time boxed release cadence for
Fineract?

So we would discuss and agree upon a DATE instead of SCOPE for 1.5.0.

Best,
M.


On Wed, 30 Sep 2020, 08:54 Aleksandar Vidakovic, 
wrote:

> Hi everyone,
>
> ... just wanted to start the discussion on what we want to include for the
> next release. Let's see if we can establish a more regular release cycle...
> looking at the current rate of contributions we should definitely have
> enough material.
>
> Please chime in and either label existing or new Jira tickets for version
> 1.5.0 or just send ideas and requests here on the mailing list.
>
> Cheers,
>
> Aleks
>

Re: Place to start contributing

[Michael Vorburger]

Hello Rob,

Thanks for your interest!

https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12335824
has got a good overview what's going on (make sure you are logged in to ASF
JIRA!), and everything we would like to do...

... https://issues.apache.org/jira/issues/?filter=12349022 got smaller
"starter" kind of issues, to "dip your feet in" - pick something?

Just listening in to and reading along questions from users on this mailing
list and jumping in wherever you can help is another great way.

Best,
M.
_______
Michael Vorburger
http://www.vorburger.ch

Re: Finereract Customization

[Michael Vorburger]

You need to run it under Java 11 instead of Java 8. The error message shown
kind of says that ("Could not target platform... Java SE 11 using tool
chain JDK 8 (1.8)"), but it's probably not clear enough?

PS: When you post on public mailing lists, could you please always
copy/paste text, instead of screenshots? That makes it easier for others to
search for such errors, and find previous answers.

On Tue, Sep 29, 2020 at 11:36 AM ጓይላና Tube  wrote:

> Hello.
> i want to create a fineract-provider jar file. When I run 헴헿헮헱헹헲현
> 헰헹헲헮헻 헯헼헼혁헝헮헿. i got this error. any help/suggestion?
>
>
> [image: fail.jpg]
>
> On Tue, 29 Sep 2020 at 09:15, Mhretaab Brehe  wrote:
>
>> Wouldn't it be good to externalize (the database password particularly
>> for fineract_tenants) to some property file or command line arguments so as
>> to avoid the password mysql?
>> when you run the artifact java -jar fineract-provider.jar
>> --db.password=your_finearact_tenants_password and some where within the
>> code to use
>> @value("${db.password}")String tenantsDbPassword;
>>
>> thanks
>>
>> On Mon, Sep 28, 2020 at 8:59 PM Michael Vorburger 
>> wrote:
>>
>>> On Mon, Sep 28, 2020 at 7:42 PM Airsay Longcon 
>>> wrote:
>>>
>>>> Hi Michael,
>>>> Thank you for the response. I understand that a straightforward java
>>>> -jar would run the jar build. I guess my question was more about how to
>>>> configure the other software like the Web-app and MySQL as I would like to
>>>> change the defaults such as the MySQL root password and port, the port
>>>> which the community/web apps will run on and some other basic changes so
>>>> that I don't have an environment that is a sitting duck for attacks
>>>>
>>>
>>> That seems very wise! :) Of course, your database shouldn't even be
>>> internet exposed at all in the first place, and only on a local IP... ;-)
>>>
>>> Jokes aside, thank you for clarifying what doc you were missing. Does
>>> https://github.com/apache/fineract/pull/1357/files help to clarify re.
>>> DB?
>>>
>>> Re. the port which the community/web apps, that may be a bigger
>>> misunderstanding - Apache Fineract does not actually include the
>>> community/web app UI at all! So java -jar fineract-provider.jar only runs
>>> the backend. If anything made you think that it does, please point us to
>>> where we say so, so that doc can be clarified. (
>>> https://github.com/apache/fineract/#instructions-to-run-using-docker-and-docker-compose
>>> however does include the community-app, but that's just for
>>> convenience/demo. That has nothing to do with the Fineract JAR/WAR itself,
>>> it's just via
>>> https://github.com/apache/fineract/blob/develop/docker-compose.yml#L59.)
>>>
>>>
>>>
>>>> On 27 Sep 2020, at 20:22, Michael Vorburger  wrote:
>>>>
>>>> 
>>>> Ese,
>>>>
>>>> On Sun, 27 Sep 2020, 20:38 Airsay Longcon, 
>>>> wrote:
>>>>
>>>>> Hi Michael,
>>>>> For a production server, how would one deploy using the jar?
>>>>>
>>>>
>>>> Simply java -jar, as per
>>>> https://github.com/apache/fineract/#instructions-to-build-the-jar-file
>>>>
>>>> Please do let us know what information you are missing re. that, so
>>>> that we may improve the README.
>>>>
>>>>
>>>> On 27 Sep 2020, at 18:48, Michael Vorburger  wrote:
>>>>>
>>>>> 
>>>>> Tube,
>>>>>
>>>>> Have you seen/are you perhaps simply looking for
>>>>> https://github.com/apache/fineract/#instructions-how-to-run-for-local-development
>>>>> ?
>>>>>
>>>>> With "./gradlew bootRun", you don't need Tomcat anymore to develop on
>>>>> Fineract!
>>>>>
>>>>> Hope this helps?
>>>>> M.
>>>>>
>>>>>
>>>>> On Sun, 27 Sep 2020, 17:55 Kelvin Ikome,  wrote:
>>>>>
>>>>>> Hi there,
>>>>>>
>>>>>> Please provide more information on what changes you are trying to
>>>>>> make which isn't working
>>>>>>
>>>>>> On Sun, Sep 27, 2020 at 4:10 PM ጓይላና Tube 
>>>>>> wrote:
>>>>>>
>>>>>>> 풉풆풍풍풐 .
>>>>>>> 푰 풘풂풏풕 풕풐 풄풖풔풕풐풎풊풛풆 풕풉풆 풃풂풄풌풆풏풅
>>>>>>> 풄풐풅풆(풋풂풗풂). 풃풖풕 풘풉풆풏 풊 풓풖풏 풕풉풆
>>>>>>> 풇풊풏풆풓풂풄풕-풑풓풐풗풊풅풆풓 풇풊풍풆. 풏풐풕풉풊풏품 풊풔
>>>>>>> 풄풉풂풏품풆풅. 풄풂풏 풚풐풖 품풖풊풅풆 풎풆 풉풐풘 풕풐
>>>>>>>  풆풅풊풕/풄풉풂풏품풆 풕풉풆 풃풂풄풌풆풏풅 풄풐풅풆 풂풏풅 풅풆풑풍풐풚
>>>>>>> 풊풏풕풐 풕풐풎풄풂풕.
>>>>>>> 푹풆품풂풓풅풔
>>>>>>>
>>>>>>

Re: [ANNOUNCE] Apache Fineract 1.4.0 Release

[Michael Vorburger]

Just tweeted https://twitter.com/ApacheFineract/status/1310688320645668865
about the 1.4.0 release, if you want to Like & RT that.

Re. a Docker container image for 1.4.0 on Docker Hub, watch
https://issues.apache.org/jira/browse/FINERACT-1164.


On Tue, Sep 22, 2020 at 12:36 AM Aleksandar Vidakovic <
chee...@monkeysintown.com> wrote:

> Hi Samuel,
>
> ... I'm working on it... should be ready as part of the release process by
> 1.5.0.
>
> In the meantime we could try to push the Docker image for 1.4.0 manually...
>
> On Mon, Sep 21, 2020 at 2:33 PM Samuel Hjelmfelt <
> s.hjelmf...@trellisfi.com> wrote:
>
>> I am not seeing a docker image tag for 14.0. Would it be possible to add
>> it to future release processes?
>>
>> https://hub.docker.com/r/apache/fineract/tags
>>
>>
>>
>> *Samuel Hjelmfelt*
>>
>> *Chief Technology Officer*
>>
>> Trellis Housing Finance Limited
>>
>> email: s.hjelmf...@trellisfi.com
>>
>> web: www.trellisfi.com
>>
>>
>>
>> *From:* Aleksandar Vidakovic 
>> *Sent:* Friday, September 18, 2020 9:31 PM
>> *To:* annou...@apache.org
>> *Cc:* dev@fineract.apache.org; u...@fineract.apache.org
>> *Subject:* [ANNOUNCE] Apache Fineract 1.4.0 Release
>>
>>
>>
>> Hi all,
>>
>>
>>
>> The Apache Fineract team would like to announce the release of Apache 
>> Fineract 1.4.0 with source and binary artifacts.
>>
>>
>>
>> Apache Fineract is an open source system for core banking as a platform. 
>> Fineract provides a reliable, robust, and affordable solution for 
>> entrepreneurs, financial institutions, and service providers to offer 
>> financial services to the world’s 2 billion under banked and unbanked.
>>
>> More details regarding Apache Fineract can be found at 
>> http://fineract.apache.org
>>
>>
>>
>> The release notes can be found here: 
>> https://cwiki.apache.org/confluence/display/FINERACT/1.4.0+-+Apache+Fineract
>>
>>
>>
>> The release artifacts can be downloaded here: 
>> https://dist.apache.org/repos/dist/release/fineract/1.4.0/
>>
>>
>>
>> Thanks!
>>
>> The Apache Fineract Team
>>
>>

Re: Finereract Customization

[Michael Vorburger]

On Mon, Sep 28, 2020 at 7:42 PM Airsay Longcon 
wrote:

> Hi Michael,
> Thank you for the response. I understand that a straightforward java -jar
> would run the jar build. I guess my question was more about how to
> configure the other software like the Web-app and MySQL as I would like to
> change the defaults such as the MySQL root password and port, the port
> which the community/web apps will run on and some other basic changes so
> that I don't have an environment that is a sitting duck for attacks
>

That seems very wise! :) Of course, your database shouldn't even be
internet exposed at all in the first place, and only on a local IP... ;-)

Jokes aside, thank you for clarifying what doc you were missing. Does
https://github.com/apache/fineract/pull/1357/files help to clarify re. DB?

Re. the port which the community/web apps, that may be a bigger
misunderstanding - Apache Fineract does not actually include the
community/web app UI at all! So java -jar fineract-provider.jar only runs
the backend. If anything made you think that it does, please point us to
where we say so, so that doc can be clarified. (
https://github.com/apache/fineract/#instructions-to-run-using-docker-and-docker-compose
however does include the community-app, but that's just for
convenience/demo. That has nothing to do with the Fineract JAR/WAR itself,
it's just via
https://github.com/apache/fineract/blob/develop/docker-compose.yml#L59.)



> On 27 Sep 2020, at 20:22, Michael Vorburger  wrote:
>
> 
> Ese,
>
> On Sun, 27 Sep 2020, 20:38 Airsay Longcon, 
> wrote:
>
>> Hi Michael,
>> For a production server, how would one deploy using the jar?
>>
>
> Simply java -jar, as per
> https://github.com/apache/fineract/#instructions-to-build-the-jar-file
>
> Please do let us know what information you are missing re. that, so that
> we may improve the README.
>
>
> On 27 Sep 2020, at 18:48, Michael Vorburger  wrote:
>>
>> 
>> Tube,
>>
>> Have you seen/are you perhaps simply looking for
>> https://github.com/apache/fineract/#instructions-how-to-run-for-local-development
>> ?
>>
>> With "./gradlew bootRun", you don't need Tomcat anymore to develop on
>> Fineract!
>>
>> Hope this helps?
>> M.
>>
>>
>> On Sun, 27 Sep 2020, 17:55 Kelvin Ikome,  wrote:
>>
>>> Hi there,
>>>
>>> Please provide more information on what changes you are trying to make
>>> which isn't working
>>>
>>> On Sun, Sep 27, 2020 at 4:10 PM ጓይላና Tube  wrote:
>>>
>>>> 풉풆풍풍풐 .
>>>> 푰 풘풂풏풕 풕풐 풄풖풔풕풐풎풊풛풆 풕풉풆 풃풂풄풌풆풏풅
>>>> 풄풐풅풆(풋풂풗풂). 풃풖풕 풘풉풆풏 풊 풓풖풏 풕풉풆
>>>> 풇풊풏풆풓풂풄풕-풑풓풐풗풊풅풆풓 풇풊풍풆. 풏풐풕풉풊풏품 풊풔
>>>> 풄풉풂풏품풆풅. 풄풂풏 풚풐풖 품풖풊풅풆 풎풆 풉풐풘 풕풐
>>>>  풆풅풊풕/풄풉풂풏품풆 풕풉풆 풃풂풄풌풆풏풅 풄풐풅풆 풂풏풅 풅풆풑풍풐풚
>>>> 풊풏풕풐 풕풐풎풄풂풕.
>>>> 푹풆품풂풓풅풔
>>>>
>>>

Re: Mifos

[Michael Vorburger]

This was already answered on
https://lists.apache.org/thread.html/rd2c0b0ce1f07cf1dbf8f5d7c70f23d2031c1250bd0d3a69fe6060ec8%40%3Cdev.fineract.apache.org%3E

I've reached out to Tube with a direct email, suspecting that he is not
correctly subscribed to the mailing list (perhaps replies going to Spam).


On Mon, Sep 28, 2020 at 4:37 PM ጓይላና Tube  wrote:

> 풉풆풍풍풐 .
> 푰 풘풂풏풕 풕풐 풄풖풔풕풐풎풊풛풆 풕풉풆 풃풂풄풌풆풏풅
> 풄풐풅풆(풋풂풗풂). 풃풖풕 풘풉풆풏 풊 풓풖풏 풕풉풆
> 풇풊풏풆풓풂풄풕-풑풓풐풗풊풅풆풓 풇풊풍풆. 풏풐풕풉풊풏품 풊풔
> 풄풉풂풏품풆풅. 풄풂풏 풚풐풖 품풖풊풅풆 풎풆 풉풐풘 풕풐
>  풆풅풊풕/풄풉풂풏품풆 풕풉풆 풃풂풄풌풆풏풅 풄풐풅풆 풂풏풅 풅풆풑풍풐풚
> 풊풏풕풐 풕풐풎풄풂풕.
> 푹풆품풂풓풅풔
>

Re: Fineract CN Improvement Proposal

[Michael Vorburger]

David, I very much like what you are outlining here.

On Sun, 27 Sep 2020, 14:30 David Yahalomi,  wrote:

> Hey,
>
> Just wanted to chime in as it is a topic we've talked about multiple times
> internally.
> There are a couple of drawbacks to using a microservice architecture that
> I think we should address. The first of which is the difficulty in managing
> the codebase and the deployed environment.
>
> Up to now, I feel like CN has failed to address those difficulties in a
> good way.
> At the moment, there is no way to run Fineract CN without a bloated
> Kubernetes / Docker Compose setup. It also takes a decent amount of time
> just to startup everything. Even if you are using a minimal set
> configuration.
> What I would expect is to have the same experience as Serverless delivers.
> Using something like serverless would definitely support the composability
> use case that is definitely there.
>
> Also, I think that co-existence with Fineract, should be a priority.
> If I were to start from scratch, I would go in a path that transforms
> Fineract to Fineract CN by doing the required work to split the
> different modules of Fineract to microservices, but without changing the
> logic or the API that is being exposed.
> An example of that would be to take the users module
> (org.apache.fineract.useradministration) of Fineract and turn it into a
> microservice but the catch here would be that once you deploy this new
> version, it migrates the related tables to the new microservice data source
> (Postgres schema?) and it takes over the /users API.
>
> This way, organizations with existing Fineract deployments could also be
> part of this new approach and could contribute their own use cases and
> requirements to the mix.
>
> Adding to this approach, I think we should consider implementing those new
> microservices with the language that has the most amount of open-source
> attention, which is Javascript or better yet, Typescript. We're for one,
> developing all of our services on top of Fineract with Typescript and get
> to enjoy the rich open-source ecosystem around it that I feel like is
> lacking in Java.
> But that's a whole other topic which I think might have way more push back.
>
> Best,
>
> David Yahalomi
> Co-Founder
>
> Rothschild Blvd 3, Tel Aviv-Yafo, Israel
> mobile: + 972 52 817 9787
> email: da...@articode.co
>   
>
>
> On Sun, Sep 27, 2020 at 2:27 PM Juhan Aasaru  wrote:
>
>> Hi!
>>
>> Fineract-CN hasn't managed to get a community that would actively push it
>> forward.
>> It could happen in the future or it could never happen.
>>
>> Anyway - rather than changing CN to a radically different direction I
>> would rather advise
>> to gather interested parties together and start from a clean perspective
>> and name it
>> something else - Fineract NS (New Start) or whatever.
>> This doesn't mean it couldn't borrow code from Fineract-CN if needed.
>> Also we have the ability to spin up new apache/fineract-* Github
>> repositories whenever needed.
>>
>> The new start could only work if there is critical mass of interested
>> parties on board from
>> the start and they work together. If there is only one company
>> outsourcing its work
>> (without others having much say what technologies to use etc) then it
>> won't be the apache
>> way to build new software and thus not a very sustainable model.
>>
>> Juhan
>>
>>
>> Kontakt James Dailey () kirjutas kuupäeval L,
>> 26. september 2020 kell 19:30:
>>
>>> Thanks Saransh for bringing this conversation forward and on-list.  I
>>> believe we need more ideas about fineract-CN, and I agree that a key
>>> 'story' is accessibility of the code to developers and avoiding the
>>> monolithic code base trap.
>>>
>>> I'll note that recently fineract 1.4 was released, a major improvement.
>>> That needed our strong focus and is a community success.
>>>
>>>  fineract-CN has not yet had the same level of focus, but I believe that
>>> it should.
>>>
>>> It's important that we also have those with fineract CN in production to
>>> help drive the roadmap. There are several and some of those folks have
>>> proposed new directions as well.  So, this is an active discussion.
>>>
>>> Previously we discussed on list the importance of the 'minimal set' of
>>> microservices.  Can you say whether you have the same list or a smaller
>>> set? Or larger set as the required microservices for a 'release'?
>>>
>>> Or how should we think about composability?
>>>
>>> In terms of your re-architecting ideas, I look forward to
>>> learning more.
>>>
>>> @jdailey
>>>
>>> On Fri, Sep 25, 2020, 3:44 AM Saransh Sharma 
>>> wrote:
>>>
 Hey folks out there , this email is intended for Fineract CN
 improvement, before setting the ground i would like to clear up a few
 things ; one this is not a separate project , this concerns overall change
 from ground up and possible variation of the existing project out there.

 Possible scenario

 We 

Re: Finereract Customization

[Michael Vorburger]

Ese,

On Sun, 27 Sep 2020, 20:38 Airsay Longcon,  wrote:

> Hi Michael,
> For a production server, how would one deploy using the jar?
>

Simply java -jar, as per
https://github.com/apache/fineract/#instructions-to-build-the-jar-file

Please do let us know what information you are missing re. that, so that we
may improve the README.


On 27 Sep 2020, at 18:48, Michael Vorburger  wrote:
>
> 
> Tube,
>
> Have you seen/are you perhaps simply looking for
> https://github.com/apache/fineract/#instructions-how-to-run-for-local-development
> ?
>
> With "./gradlew bootRun", you don't need Tomcat anymore to develop on
> Fineract!
>
> Hope this helps?
> M.
>
>
> On Sun, 27 Sep 2020, 17:55 Kelvin Ikome,  wrote:
>
>> Hi there,
>>
>> Please provide more information on what changes you are trying to make
>> which isn't working
>>
>> On Sun, Sep 27, 2020 at 4:10 PM ጓይላና Tube  wrote:
>>
>>> 풉풆풍풍풐 .
>>> 푰 풘풂풏풕 풕풐 풄풖풔풕풐풎풊풛풆 풕풉풆 풃풂풄풌풆풏풅
>>> 풄풐풅풆(풋풂풗풂). 풃풖풕 풘풉풆풏 풊 풓풖풏 풕풉풆
>>> 풇풊풏풆풓풂풄풕-풑풓풐풗풊풅풆풓 풇풊풍풆. 풏풐풕풉풊풏품 풊풔
>>> 풄풉풂풏품풆풅. 풄풂풏 풚풐풖 품풖풊풅풆 풎풆 풉풐풘 풕풐
>>>  풆풅풊풕/풄풉풂풏품풆 풕풉풆 풃풂풄풌풆풏풅 풄풐풅풆 풂풏풅 풅풆풑풍풐풚
>>> 풊풏풕풐 풕풐풎풄풂풕.
>>> 푹풆품풂풓풅풔
>>>
>>

Re: Finereract Customization

[Michael Vorburger]

Tube,

Have you seen/are you perhaps simply looking for
https://github.com/apache/fineract/#instructions-how-to-run-for-local-development
?

With "./gradlew bootRun", you don't need Tomcat anymore to develop on
Fineract!

Hope this helps?
M.


On Sun, 27 Sep 2020, 17:55 Kelvin Ikome,  wrote:

> Hi there,
>
> Please provide more information on what changes you are trying to make
> which isn't working
>
> On Sun, Sep 27, 2020 at 4:10 PM ጓይላና Tube  wrote:
>
>> 풉풆풍풍풐 .
>> 푰 풘풂풏풕 풕풐 풄풖풔풕풐풎풊풛풆 풕풉풆 풃풂풄풌풆풏풅
>> 풄풐풅풆(풋풂풗풂). 풃풖풕 풘풉풆풏 풊 풓풖풏 풕풉풆
>> 풇풊풏풆풓풂풄풕-풑풓풐풗풊풅풆풓 풇풊풍풆. 풏풐풕풉풊풏품 풊풔
>> 풄풉풂풏품풆풅. 풄풂풏 풚풐풖 품풖풊풅풆 풎풆 풉풐풘 풕풐
>>  풆풅풊풕/풄풉풂풏품풆 풕풉풆 풃풂풄풌풆풏풅 풄풐풅풆 풂풏풅 풅풆풑풍풐풚
>> 풊풏풕풐 풕풐풎풄풂풕.
>> 푹풆품풂풓풅풔
>>
>

Fwd: [jira] Subscription: Fineract Blockers

[Michael Vorburger]

Hello everyone,

Below is the current list of blocker bugs.

Contributions with fixes to any of these are very welcome!

M.
___
Michael Vorburger
http://www.vorburger.ch


-- Forwarded message -
From: 
Date: Fri, Sep 25, 2020 at 3:01 AM
Subject: [jira] Subscription: Fineract Blockers
To: 




Issue Subscription
Filter: Fineract Blockers
<https://issues.apache.org/jira/issues/?filter=12349014> (11 issues)
Subscriber: vorburger
T Patch Info Key Summary Assignee Reporter P Status Resolution Created Updated
Due Development
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1080>
FINERACT-1080 <https://issues.apache.org/jira/browse/FINERACT-1080>

WHOLE_TERM case is missing logic?
<https://issues.apache.org/jira/browse/FINERACT-1080>
*Unassigned* Percy Ashu
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Percy%20Ashu>
[image:
Blocker] Open *Unresolved* 07/Jul/20 07/Jul/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1086>
FINERACT-1086 <https://issues.apache.org/jira/browse/FINERACT-1086>

JpaOptimisticLockingFailureException at
LoanSchedularServiceImpl.recalculateInterest() - requires retry logic?
<https://issues.apache.org/jira/browse/FINERACT-1086>
*Unassigned* Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Open *Unresolved* 11/Jul/20 11/Jul/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1036>
FINERACT-1036 <https://issues.apache.org/jira/browse/FINERACT-1036>

NullPointerException at DocumentManagementApiResource.createDocument()
<https://issues.apache.org/jira/browse/FINERACT-1036>
*Unassigned* Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Open *Unresolved* 14/Jun/20 25/Jul/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1121>
FINERACT-1121 <https://issues.apache.org/jira/browse/FINERACT-1121>

NoSuchElementException at
AbstractLoanScheduleGenerator.checkIfFirstRepaymentDateisOnHolidayOrNonWorkingDay
<https://issues.apache.org/jira/browse/FINERACT-1121>
*Unassigned* Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Open *Unresolved* 20/Aug/20 20/Aug/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1085>
FINERACT-1085 <https://issues.apache.org/jira/browse/FINERACT-1085>

JournalEntryInvalidException: Journal entry cannot be made prior to last
account closing date for the branch at
org.apache.fineract.accounting.journalentry.service.AccountingProcessorHelper.checkForBranchClosures()
<https://issues.apache.org/jira/browse/FINERACT-1085>
*Unassigned* Michael Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Open *Unresolved* 11/Jul/20 12/Sep/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1037>
FINERACT-1037 <https://issues.apache.org/jira/browse/FINERACT-1037>

FileNotFoundException:
/home/tomcat/.fineract/DefaultDemoTenant/documents/CLIENTS_PERSON/null/sf5694ypszb/something.xls
<https://issues.apache.org/jira/browse/FINERACT-1037>
Petri Tuomola
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ptuomola> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] In Progress *Unresolved* 14/Jun/20 20/Sep/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1155>
FINERACT-1155 <https://issues.apache.org/jira/browse/FINERACT-1155>

NPE at AddressWritePlatformServiceImpl.addNewClientAddress()
<https://issues.apache.org/jira/browse/FINERACT-1155>
Manthan Surkar
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Manthan> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] Open *Unresolved* 22/Sep/20 22/Sep/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1089>
FINERACT-1089 <https://issues.apache.org/jira/browse/FINERACT-1089>

Operation not allowed for a result set of type ResultSet.TYPE_FORWARD_ONLY
in InterestRateChartReadPlatformServiceImpl
<https://issues.apache.org/jira/browse/FINERACT-1089>
Percy Ashu
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Percy%20Ashu>
Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Blocker] In Progress *Unresolved* 11/Jul/20 23/Sep/20
[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-932>
FINERACT-932 <https://issues.apache.org/jira/browse/FINERACT-932>

Parent Issue for Error Logs seeing during "normal" usage (e.g. on
fineract.dev) <https://issues.apache.org/jira/browse/FINERACT-932>
Michael Vorburger
<https://issues.apache.org/jira/secure/ViewPr

Re: API ACCESS

[Michael Vorburger]

On Thu, 24 Sep 2020, 10:24 Sifiso,  wrote:

> Thanks Michael, that has helped for me.
>

Great to hear.

I am trying to add new mapper values to the loans template for loans on
> screen reports. However when I add the API for the new mapper values under
> advanced options it appears blank.
>

Blank in a UI? It's easier for us to debug if you use the REST API only.

If I am on a working loans template and I add a client mapper value that
> already exists from the client templates it returns blank fields.
> For example addind this to a loan template
> Mapper - client
> Mapper value - clients/{{clientId}}?tenantIdentifier=default
> eg {{client.officeName}} does not return a value and its blank
>
> How can I best go around this?
>

I'm personally not very familiar with this functionality.

To help, it would be best if you could describe how to reproduce this
showing us e.g. a series of curl commands, or a Postman file.


> Regards,
> Sifiso
>
> On 24 September 2020 at 09:00:50 +02:00, Michael Vorburger <
> m...@vorburger.ch> wrote:
>
> Ronele,
>
> As per direct email exchange, hopefully you have meanwhile successfully
> subscribed to this mailing list, and are now receiving this:
>
> If you're getting a 404, then you're probably just using the wrong URL. It
> had to be e.g.
>
>
> https://demo.fineract.dev/fineract-provider/api/v1/clients?tenantIdentifier=default
>
> Does this help?
>
> Regards,
> M.
>
>
> On Tue, 22 Sep 2020, 20:48 Michael Vorburger,  wrote:
>
> On Tue, 22 Sep 2020, 16:06 Ronele Galamgam, 
> wrote:
>
>
> Hi,
>
>
>
> How can we access fineract api in our own domain? is there any
> documentation for this one?
>
> We have fineract running and can access the documentation in
> api-docs/apiLive.htm
>
> but when trying to access a sample request, seems denied.
>
>
> Can you provide more specific details about how exactly what is denied?
>
> You can use https://www.fineract.dev to try it out, and illustrate what
> you mean.
>
> May I know how to do this?
>
>
>
> Thanks!
>
>
>
> *Ronele Galamgam*
>
> DevOps Engineer
>
> *quantumcrowd.io <http://quantumcrowd.io/>*
>
>
>

Re: We are listening

[Michael Vorburger]

On Thu, 24 Sep 2020, 14:04 ጓይላና Tube,  wrote:

> Hi everone!
> i want to build war file from fineract-provider.
>

https://github.com/apache/fineract/#instructions-to-build-a-war-file

But WHY do you still want to build the WAR, which you then still have to
deploy to Tomcat?! It's much better and recommended to instead follow
https://github.com/apache/fineract/#instructions-to-build-the-jar-file to
build the JAR which you run much more easily with java -jar.

can someone guide me how to do this in intelliJ IDE or eclipse?
>

No need for an IDE for building the JAR (or WAR), just CLI. IDE for coding,
only.

Regards.
>
> On Tue, 22 Sep 2020 at 23:19, ጓይላና Tube  wrote:
>
>> Thanks, I'll check it out.
>>
>> On Tue, 22 Sep 2020 at 20:42, Michael Vorburger 
>> wrote:
>>
>>> +Manthan:
>>>
>>> On Tue, Sep 22, 2020 at 8:42 AM Mexina Daniel 
>>> wrote:
>>>
>>>> Hi Michael
>>>>
>>>> See the file attached from Tube.
>>>>
>>>> Seems it wasn't attached in the mail list.
>>>>
>>> oh, I had not noticed that (it's best to point out if something is
>>> attached). So here is the error, it's better to include it in the email
>>> body text, so that search engines can find it:
>>>
>>> java.lang.NullPointerException
>>> at 
>>> org.apache.fineract.infrastructure.security.utils.SQLInjectionValidator.validateSQLInput(SQLInjectionValidator.java:36)
>>> at 
>>> org.apache.fineract.infrastructure.security.utils.ColumnValidator.validateSqlInjection(ColumnValidator.java:95)
>>> at 
>>> org.apache.fineract.infrastructure.dataqueries.service.ReadWriteNonCoreDataServiceImpl.retrieveDataTableGenericResultSet(ReadWriteNonCoreDataServiceImpl.java:1190)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at 
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>> at 
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:498)
>>> at 
>>> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
>>> at 
>>> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201)
>>> at com.sun.proxy.$Proxy145.retrieveDataTableGenericResultSet(Unknown 
>>> Source)
>>> at 
>>> org.apache.fineract.infrastructure.dataqueries.api.DatatablesApiResource.getDatatable(DatatablesApiResource.java:174)
>>>
>>> if we look at
>>> https://github.com/apache/fineract/blob/develop/fineract-provider/src/main/java/org/apache/fineract/infrastructure/dataqueries/service/ReadWriteNonCoreDataServiceImpl.java,
>>> we can see that line 1190 no longer calls validateSqlInjection(), so this
>>> is presumably from an older (or forked) version of that code. But the only
>>> use of validateSqlInjection() in ReadWriteNonCoreDataServiceImpl has now
>>> moved to line 1235. Assuming that's the one, then this problem has
>>> something to do with the order parameter to the
>>> {datatable}/{apptableId}/{datatableId} REST API... what did you specify as
>>> "order"? Try simply without order for a test - it probably works better,
>>> right?
>>>
>>> BTW we (Manthan) fixed something which may well be (I'm not 100% sure)
>>> related to this in 1.4.0 - check out
>>> https://issues.apache.org/jira/browse/FINERACT-1066. Can you try
>>> upgrading to and using 1.4.0?
>>>
>>> PS we're trying to eventually remove the entire SQLInjectionValidator
>>> altogether, watch https://issues.apache.org/jira/browse/FINERACT-1095..
>>> there's more work left to achieve that, including e.g.
>>> https://issues.apache.org/jira/browse/FINERACT-1058. Manthan, when you
>>> got to that, or anyone else interested in joining the party and helping re.
>>> this, looks to me like ReadWriteNonCoreDataServiceImpl is another place
>>> that could benefit from using our SqlBuilder utility instead of the buggy
>>> SQLInjectionValidator.
>>>
>>> Daniel & Tube, hope this helps? Let me know if it did, always happy to
>>> hear.
>>>
>>>> Best Regards
>>>> ---
>>>>
>>>> Mexina Daniel
>>>>
>>>> Managing Director
>>>>
>>>> Singo Africa Limited ~~ *adding value*
>>>>
>>>> Magomeni-Makumbusho | Morogoro Rd/Ruaha Str.
&g

Re: API ACCESS

[Michael Vorburger]

Ronele,

As per direct email exchange, hopefully you have meanwhile successfully
subscribed to this mailing list, and are now receiving this:

If you're getting a 404, then you're probably just using the wrong URL. It
had to be e.g.

https://demo.fineract.dev/fineract-provider/api/v1/clients?tenantIdentifier=default

Does this help?

Regards,
M.


On Tue, 22 Sep 2020, 20:48 Michael Vorburger,  wrote:

> On Tue, 22 Sep 2020, 16:06 Ronele Galamgam, 
> wrote:
>
>> Hi,
>>
>>
>>
>> How can we access fineract api in our own domain? is there any
>> documentation for this one?
>>
>> We have fineract running and can access the documentation in
>> api-docs/apiLive.htm
>>
>> but when trying to access a sample request, seems denied.
>>
>
> Can you provide more specific details about how exactly what is denied?
>
> You can use https://www.fineract.dev to try it out, and illustrate what
> you mean.
>
> May I know how to do this?
>>
>>
>>
>> Thanks!
>>
>>
>>
>> *Ronele Galamgam*
>>
>> DevOps Engineer
>>
>> *quantumcrowd.io <http://quantumcrowd.io/>*
>>
>

FINERACT-1155 NPE at AddressWritePlatformServiceImpl.addNewClientAddress()

[Michael Vorburger]

Hello, any volunteers for taking up
https://issues.apache.org/jira/browse/FINERACT-1155?
___
Michael Vorburger
http://www.vorburger.ch

Re: We are listening

[Michael Vorburger]

+Manthan:

On Tue, Sep 22, 2020 at 8:42 AM Mexina Daniel  wrote:

> Hi Michael
>
> See the file attached from Tube.
>
> Seems it wasn't attached in the mail list.
>
oh, I had not noticed that (it's best to point out if something is
attached). So here is the error, it's better to include it in the email
body text, so that search engines can find it:

java.lang.NullPointerException
at 
org.apache.fineract.infrastructure.security.utils.SQLInjectionValidator.validateSQLInput(SQLInjectionValidator.java:36)
at 
org.apache.fineract.infrastructure.security.utils.ColumnValidator.validateSqlInjection(ColumnValidator.java:95)
at 
org.apache.fineract.infrastructure.dataqueries.service.ReadWriteNonCoreDataServiceImpl.retrieveDataTableGenericResultSet(ReadWriteNonCoreDataServiceImpl.java:1190)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at 
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201)
at com.sun.proxy.$Proxy145.retrieveDataTableGenericResultSet(Unknown 
Source)
at 
org.apache.fineract.infrastructure.dataqueries.api.DatatablesApiResource.getDatatable(DatatablesApiResource.java:174)

if we look at
https://github.com/apache/fineract/blob/develop/fineract-provider/src/main/java/org/apache/fineract/infrastructure/dataqueries/service/ReadWriteNonCoreDataServiceImpl.java,
we can see that line 1190 no longer calls validateSqlInjection(), so this
is presumably from an older (or forked) version of that code. But the only
use of validateSqlInjection() in ReadWriteNonCoreDataServiceImpl has now
moved to line 1235. Assuming that's the one, then this problem has
something to do with the order parameter to the
{datatable}/{apptableId}/{datatableId} REST API... what did you specify as
"order"? Try simply without order for a test - it probably works better,
right?

BTW we (Manthan) fixed something which may well be (I'm not 100% sure)
related to this in 1.4.0 - check out
https://issues.apache.org/jira/browse/FINERACT-1066. Can you try upgrading
to and using 1.4.0?

PS we're trying to eventually remove the entire SQLInjectionValidator
altogether, watch https://issues.apache.org/jira/browse/FINERACT-1095..
there's more work left to achieve that, including e.g.
https://issues.apache.org/jira/browse/FINERACT-1058. Manthan, when you got
to that, or anyone else interested in joining the party and helping re.
this, looks to me like ReadWriteNonCoreDataServiceImpl is another place
that could benefit from using our SqlBuilder utility instead of the buggy
SQLInjectionValidator.

Daniel & Tube, hope this helps? Let me know if it did, always happy to hear.

> Best Regards
> ---
>
> Mexina Daniel
>
> Managing Director
>
> Singo Africa Limited ~~ *adding value*
>
> Magomeni-Makumbusho | Morogoro Rd/Ruaha Str.
>
> Opp. Usalama BRT | Watumishi House, Wing B,  Gnd Flr.
>
> P.O BOX 78908 | 14121 Dar es salaam
>
> +255 71 211 0791
>
> amala.co.tz | singo.africa
>
>
>
> On 14-09-2020 14:45, Michael Vorburger wrote:
>
> As far as one can tell from reading the email thread below, this just
> seems to be a question about how to use data tables feature?
>
> I'm not seeing anything below offering any details about anything related
> to an SQL Injection vulnerability.
>
>
> On Mon, 14 Sep 2020, 13:34 Mexina Daniel,  wrote:
>
>> Hello Tube
>>
>> I have cc'd the community so that if there is anyone with a solution can
>> share.
>>
>> Hello Community
>>
>> Can someone help as i haven't yet understood what could be the problem, i
>> have attached the log file he shared.
>>
>> I can see there is an issue with SQLInjection.
>>
>> Best Regards
>> ---
>>
>> Mexina Daniel
>>
>> Managing Director
>>
>> Singo Africa Limited ~~ *adding value*
>>
>> Magomeni-Makumbusho | Morogoro Rd/Ruaha Str.
>>
>> Opp. Usalama BRT | Watumishi House, Wing B,  Gnd Flr.
>>
>> P.O BOX 78908 | 14121 Dar es salaam
>>
>> +255 71 211 0791
>>
>> amala.co.tz | singo.africa
>>
>>
>>
>> On 14-09-2020 13:00, ጓይላና Tube wrote:
>>
>> hello
>>
>> Here is the log file.
>>
>> Best Regards
>>
>> On Mon, 14 Sep 2020 at 09:19, Mexina Daniel  wrote:
>>
>>> Hello
>>>
>>> Can you share the log file to see what is the error?
>>>
>&g

Re: API ACCESS

[Michael Vorburger]

On Tue, 22 Sep 2020, 16:06 Ronele Galamgam, 
wrote:

> Hi,
>
>
>
> How can we access fineract api in our own domain? is there any
> documentation for this one?
>
> We have fineract running and can access the documentation in
> api-docs/apiLive.htm
>
> but when trying to access a sample request, seems denied.
>

Can you provide more specific details about how exactly what is denied?

You can use https://www.fineract.dev to try it out, and illustrate what you
mean.

May I know how to do this?
>
>
>
> Thanks!
>
>
>
> *Ronele Galamgam*
>
> DevOps Engineer
>
> *quantumcrowd.io *
>

Re: We are listening

[Michael Vorburger]

As far as one can tell from reading the email thread below, this just seems
to be a question about how to use data tables feature?

I'm not seeing anything below offering any details about anything related
to an SQL Injection vulnerability.


On Mon, 14 Sep 2020, 13:34 Mexina Daniel,  wrote:

> Hello Tube
>
> I have cc'd the community so that if there is anyone with a solution can
> share.
>
> Hello Community
>
> Can someone help as i haven't yet understood what could be the problem, i
> have attached the log file he shared.
>
> I can see there is an issue with SQLInjection.
>
> Best Regards
> ---
>
> Mexina Daniel
>
> Managing Director
>
> Singo Africa Limited ~~ *adding value*
>
> Magomeni-Makumbusho | Morogoro Rd/Ruaha Str.
>
> Opp. Usalama BRT | Watumishi House, Wing B,  Gnd Flr.
>
> P.O BOX 78908 | 14121 Dar es salaam
>
> +255 71 211 0791
>
> amala.co.tz | singo.africa
>
>
>
> On 14-09-2020 13:00, ጓይላና Tube wrote:
>
> hello
>
> Here is the log file.
>
> Best Regards
>
> On Mon, 14 Sep 2020 at 09:19, Mexina Daniel  wrote:
>
>> Hello
>>
>> Can you share the log file to see what is the error?
>>
>> Best Regards
>> ---
>>
>> Mexina Daniel
>>
>> Managing Director
>>
>> Singo Africa Limited ~~ *adding value*
>>
>> Magomeni-Makumbusho | Morogoro Rd/Ruaha Str.
>>
>> Opp. Usalama BRT | Watumishi House, Wing B,  Gnd Flr.
>>
>> P.O BOX 78908 | 14121 Dar es salaam
>>
>> +255 71 211 0791
>>
>> amala.co.tz | singo.africa
>>
>>
>>
>> On 13-09-2020 18:22, ጓይላና Tube wrote:
>>
>>
>>
>> On Sun, 13 Sep 2020 at 16:19, ጓይላና Tube  wrote:
>>
>>> Hello
>>>
>>> i have installed mifos platform locally. but i got the same error in
>>> Mifos demo and locally installed mifos. Datatables are not displaying &
>>> showing red rectangle
>>>
>>> Below is a screenshot of the error
>>>
>>> Regards
>>>
>>>
>>> On Sun, 13 Sep 2020 at 11:13, Mexina Daniel  wrote:
>>>
 Hello

 Have you tried in a demo of Mifos and it's not displayed or you are
 talking of your system installed locally?

 Best Regards

 On 12 Sep 2020 23:22, ጓይላና Tube  wrote:

 Thank You for your resposne

  #Data tables created for Group, Client, Loan and Savings account is
 not getting displayed in the particular General pages (eg. datatable
 created for client is not displaying in Client general page),
 can you suggest me the solution to solve this problem?

 Best Regards


 On Sat, 12 Sep 2020 at 21:18, Mexina Daniel 
 wrote:

 Hello

 Go ahead and ask.

 Best Regards

 On 12 Sep 2020 19:57, ጓይላና Tube  wrote:

 this is tesfahiwet software developer from mekelle, ethiopia. i want to
 ask you some questions about mifos platform.
 thank you for your response

 On Sat, 12 Sep 2020 at 17:55, ጓይላና Tube  wrote:

 Thank you for your response.

 On Sat, 12 Sep 2020 at 17:02, Mexina Daniel 
 wrote:

 Hello

 We have received your text through our chat.

 May we know how we can help you?

 Best Regards

 Mexina Daniel

Re: Join the Fineract Issues Mailing to get notifications on bug and new feature requests

[Michael Vorburger]

That's a great tip! It makes me think of something related that's perhaps
worth pointing out here, if you prefer not to receive more emails, but just
want to know where you can go to look at what's going on in this project:

Simply set yourself a reminder to occasionally have a look at that Activity
Stream list in the middle of the Dashboard on
https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12335824.
It should look something like this for you:
https://drive.google.com/file/d/1WbwIvVTJ02ugQKK4cusbD87Vtc4-KBVv/view?usp=sharing
.

If the middle column on the above linked Dashboard is completely blank
white for you, then you simply need to sign up for a log at the ASF JIRA
here https://issues.apache.org/jira/secure/Signup!default.jspa. It's still
free this month, so hurry up! ;-) [This is a joke; it's always free.]

On Thu, Aug 27, 2020 at 10:26 PM Awasum Yannick 
wrote:

> Hi All,
>
> If you are a Developer or interested in issues, bug reports and new
> feature requests opened on the Fineract and Fineract CN JIRA, then
> please join the iss...@fineract.apache.org mailing list by sending a
> blank mail here: issues-subscr...@fineract.apache.org and follow the
> instructions.
>
>  History: https://lists.apache.org/list.html?iss...@fineract.apache.org
>
> This way you will get new updates when new bug reports, issues and
> feature requests are created, updated or closed. You will be able to
> decide on what to work on and know when something has been fixed or
> status changed.
>
> Thanks.
> Awasum
>

Re: [VOTE] [APACHE FINERACT] 1.4.0 for release

[Michael Vorburger]

+1 (binding, as PMC member)


On Thu, Sep 10, 2020 at 3:42 AM Aleksandar Vidakovic <
chee...@monkeysintown.com> wrote:

> Hello everyone,
>
> We have created Apache Fineract 1.4.0 release, with the artifacts below up
> for a vote.
>
> It fixes the following issues:
> https://cwiki.apache.org/confluence/display/FINERACT/1.4.0+-+Apache+Fineract
>
> Source & Binary files :
> https://dist.apache.org/repos/dist/dev/fineract/1.4.0/
>
> Tag to be voted on (rc#):
> https://git-wip-us.apache.org/repos/asf?p=fineract.git;a=commit;h=refs/heads/1.4.0
>
> Fineract's KEYS containing the PGP key we used to sign the release:
> https://dist.apache.org/repos/dist/dev/fineract/KEYS
>
> Note that this release contains source and binary artifacts.
>
> This vote will be open for 72 hours:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Thanks and cheers,
>
> Aleks
>

Checkstyle and Error Prone -- Fwd: [jira] Subscription: Fineract Resolved Last Week

[Michael Vorburger]

14 issues resolved last week, whoot whoot!

Of particular noteworthiness below are Manthan's Checkstyle FINERACT-821
<https://issues.apache.org/jira/browse/FINERACT-821> and FINERACT-942
<https://issues.apache.org/jira/browse/FINERACT-942> and Percy's Error
Prone FINERACT-822 <https://issues.apache.org/jira/browse/FINERACT-822>.
All that work over the last months, culminating in closing those issues
this week for the upcoming 1.4.0, greatly improved Fineract code quality.
Crucially, Manthan and Percy not only fixed related bugs those tools found
during their GSoC projects (which are currently being wrapped up), but both
Checkstyle and Error Prone are meanwhile enabled and enforced for builds on
each Pull Request - and will thus continue to help automatically keep up
code quality in the project's future.

Several Swagger related issues also show up below, and we will be
communicating more about that in a separate email thread hopefully soon.


-- Forwarded message -
From: 
Date: Fri, 28 Aug 2020, 03:01
Subject: [jira] Subscription: Fineract Resolved Last Week
To: 




Issue Subscription
Filter: Fineract Resolved Last Week
<https://issues.apache.org/jira/issues/?filter=12349018> (14 issues)
Subscriber: vorburger
T Patch Info Key Summary Assignee Reporter P Status Resolution Created Updated
Due Development
[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-1129>
FINERACT-1129 <https://issues.apache.org/jira/browse/FINERACT-1129>

Gradle task to create release package
<https://issues.apache.org/jira/browse/FINERACT-1129>
Aleksandar Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> Aleksandar
Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> [image:
Minor] Resolved Fixed 25/Aug/20 28/Aug/20 26/Aug/20
[image: Sub-task] <https://issues.apache.org/jira/browse/FINERACT-1134>
FINERACT-1134 <https://issues.apache.org/jira/browse/FINERACT-1134>

FINERACT-1129 <https://issues.apache.org/jira/browse/FINERACT-1129> Backport
FINERACT-1129 to release branch 1.4.0
<https://issues.apache.org/jira/browse/FINERACT-1134>
Aleksandar Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> Aleksandar
Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> [image:
Blocker] Resolved Fixed 27/Aug/20 27/Aug/20 27/Aug/20
[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-1101>
FINERACT-1101 <https://issues.apache.org/jira/browse/FINERACT-1101>

Swagger CodeGen Test Build using Gradle instead of Maven
<https://issues.apache.org/jira/browse/FINERACT-1101>
Aleksandar Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Minor] Resolved Fixed 02/Aug/20 27/Aug/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1133>
FINERACT-1133 <https://issues.apache.org/jira/browse/FINERACT-1133>

Swagger generated library incorrect documentation
<https://issues.apache.org/jira/browse/FINERACT-1133>
Aleksandar Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> Chinmay
Kulkarni
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Grandolf49>
[image:
Major] Resolved Fixed 26/Aug/20 27/Aug/20
[image: Sub-task] <https://issues.apache.org/jira/browse/FINERACT-1137>
FINERACT-1137 <https://issues.apache.org/jira/browse/FINERACT-1137>

FINERACT-1129 <https://issues.apache.org/jira/browse/FINERACT-1129> Backport
Gradle task to create release package to release branch 1.4.0
<https://issues.apache.org/jira/browse/FINERACT-1137>
Aleksandar Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> Aleksandar
Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> [image:
Major] Closed Fixed 27/Aug/20 27/Aug/20 27/Aug/20
[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-1105>
FINERACT-1105 <https://issues.apache.org/jira/browse/FINERACT-1105>

Swagger generates invalid Open API Specification file
<https://issues.apache.org/jira/browse/FINERACT-1105>
Chinmay Kulkarni
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Grandolf49>
Chinmay
Kulkarni
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Grandolf49>
[image:
Minor] Resolved Fixed 04/Aug/20 26/Aug/20
[image: Sub-task] <https://issues.apache.org/jira/browse/FINERACT-838>
FINERACT-838 <https://issues.apache.org/jira/browse/FINERACT-838>

FINERACT-733 <https://issues.apache.org/jira/browse/FINERACT-733> Swagger
generated client libraries
<https://issues.apache.org/jira/browse/FINERACT-838>
Chinmay Kulkarni
<https://issues.apache.org/jira/secure/ViewProfile.jspa?n

Re: Fineract 1.4.0 release branch

[Michael Vorburger]

[I'm dropping people on Cc and bringing this thread back to the mailing
list only]

On Wed, Aug 26, 2020 at 6:49 AM James Dailey  wrote:

> I'm following this discussion. Or trying to. Thanks for keeping this
> onlist and in the jira tickets. Really appreciate it.
>
> Q on swagger client: Is that already in develop branch?
>

yup, see https://github.com/apache/fineract/#apache-fineract-platform-api
=>
https://github.com/apache/fineract/blob/develop/docs/developers/swagger/client.md

Background in https://issues.apache.org/jira/browse/FINERACT-838 et al.

Big Thank You shout out to Chinmay Kulkarni for his work on this topic!


> (Only partly ?)  If so, will excluding that from this release create
> upstream issues for other dev efforts that rely on that ( if any?).
>
> +1 on the 'cherry picking from accepted-to- develop branch code w PR
> raised against 1.4' approach. (That's a mouthful.)
>
>
>
>
>
> On Tue, Aug 25, 2020, 3:39 PM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> Re: last paragraph: thanks Michael; this clarifies a couple of questions
>> I had left... and I agree with an earlier date for release 1.5.0 (and
>> following)... otherwise it'll also be too much work for anyone who wants to
>> upgrade from a previous version.
>>
>> Will add the gist of this conversation to the release document.
>>
>> Thanks again
>>
>>
>> On Wed, Aug 26, 2020 at 12:24 AM Michael Vorburger 
>> wrote:
>>
>>> On Wed, Aug 26, 2020 at 12:20 AM Aleksandar Vidakovic <
>>> chee...@monkeysintown.com> wrote:
>>>
>>>> Hi Michael,
>>>>
>>>> ... I'm almost there... my release task generates also GPG signatures
>>>> for verification (tested them... all correct).
>>>>
>>>
>>> cool!
>>>
>>>
>>>> Only thing that is left is to include the generated API client JAR; at
>>>> the moment only the sources are created, but no JAR artifact is available.
>>>> Any idea how to proceed here (as this is a release I guess we shouldn't
>>>> include just the client sources)?
>>>>
>>>> All details here: https://issues.apache.org/jira/browse/FINERACT-1129
>>>> (contains also link to sources)
>>>>
>>>
>>> I'll engage (and answer above re. client) on that JIRA.
>>>
>>>
>>>> Cheers
>>>>
>>>> On Tue, Aug 25, 2020 at 9:30 PM Aleksandar Vidakovic <
>>>> chee...@monkeysintown.com> wrote:
>>>>
>>>>> Alright Michael... the first list it is (WAR, server and client JAR,
>>>>> and README). I'll create a PR for the Gradle task.
>>>>>
>>>>> One more question: I intend to git cherry pick features from develop
>>>>> that arrived after I created the release branch... is that OK or do you
>>>>> guys usually use different approaches (like rebase)?
>>>>>
>>>>
>>> Either is fine with me personally, but I think the real question here is
>>> more another one:
>>>
>>> Do you want to cherry-pick very selectively just a limited few
>>> particular last minute changes, or just rebase to catch up with everything
>>> on develop. The latter would in practice really mean that we just branched
>>> too soon? ;-) Personally I probably would therefore go for the former (and
>>> cherry-pick, only).
>>>
>>> There's always more coming in, and that's fine. Can't stop progress. You
>>> just draw a line in the sand somewhere. There will always be the next
>>> release after. Maybe we can have a 1.5.0 sooner after 1.4.0 than we had
>>> after 1.3.0? :) Otherwise we'll never release... ;-)
>>>
>>> A related interesting question is perhaps if YOU (as the RM) should be
>>> the one that raises PR for such cherry-picks. I would argue that you
>>> shouldn't have to... you "did your job" of the process. You've sent the
>>> heads up email, and nobody objected to the timeline you've proposed. Now I
>>> personally would probably just let any contributors who still absolutely
>>> WANT to get anything into 1.4.0 last minute raise PRs for the 1.4.0 branch
>>> themselves (and resolve conflicts, if any; and get them to build).
>>> https://github.com/apache/fineract/pull/1272 was a great working
>>> example of that; as a committer to the project, you can Rebase Merge those
>>> yourself in the future (if they are also on develop; I suggest that we do
>>> not put anything on 1.4.0 that isn't

Fwd: [jira] Subscription: Fineract Resolved Last Week

[Michael Vorburger]

Below are 3 issues which were fixed 2 weeks ago - thanks Manoj, we hope to
see more from you!


-- Forwarded message -
From: 
Date: Fri, Aug 14, 2020 at 3:01 AM
Subject: [jira] Subscription: Fineract Resolved Last Week
To: 




Issue Subscription
Filter: Fineract Resolved Last Week
 (3 issues)
Subscriber: vorburger
T Patch Info Key Summary Assignee Reporter P Status Resolution Created Updated
Due Development
[image: Bug] 
FINERACT-1106 

Rescheduling a loan ignores non-working days/holidays

Manoj  Ed
Cable 
[image:
Major] Resolved Fixed 04/Aug/20 14/Aug/20
[image: Bug] 
FINERACT-1107 

Rescheduling a loan with a payment day on 29, 30, 31 of the month to the
first/second of the following month doesn’t work as expected

Manoj  Ed
Cable 
[image:
Major] Resolved Fixed 04/Aug/20 14/Aug/20
[image: Sub-task] 
FINERACT-1098 

FINERACT-849  Add
JpaSystemException as a JPA transaction exception

Yemdjih Kaze Nasser
 Yemdjih
Kaze Nasser
 [image:
Major] Resolved Fixed 30/Jul/20 14/Aug/20
You may edit this subscription here
.


This message was sent by Atlassian Jira (v8.3.4#803005-sha1:1f96e09)
[image: Atlassian logo]

Fwd: [jira] Subscription: Fineract Resolved Last Week

[Michael Vorburger]

Here are LAST (not this) week's 8 issues resolved - thanks!


-- Forwarded message -
From: 
Date: Fri, Aug 21, 2020 at 3:07 AM
Subject: [jira] Subscription: Fineract Resolved Last Week
To: 




Issue Subscription
Filter: Fineract Resolved Last Week
<https://issues.apache.org/jira/issues/?filter=12349018> (8 issues)
Subscriber: vorburger
T Patch Info Key Summary Assignee Reporter P Status Resolution Created Updated
Due Development
[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-1116>
FINERACT-1116 <https://issues.apache.org/jira/browse/FINERACT-1116>

Add release of already onhold amount from interoperation transaction
<https://issues.apache.org/jira/browse/FINERACT-1116>
Aleksandar Vidakovic
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aleks> Zoltán
Nébli <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ezolnbl>
[image:
Major] Resolved Fixed 12/Aug/20 14/Aug/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1109>
FINERACT-1109 <https://issues.apache.org/jira/browse/FINERACT-1109>

Inability to reschedule when interest accrued larger than EMI
<https://issues.apache.org/jira/browse/FINERACT-1109>
Manoj <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=fynmanoj> Ed
Cable <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=edcable>
[image:
Major] Resolved Fixed 04/Aug/20 20/Aug/20
[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-1108>
FINERACT-1108 <https://issues.apache.org/jira/browse/FINERACT-1108>

Custom Installment amount for range of planned payments
<https://issues.apache.org/jira/browse/FINERACT-1108>
Manoj <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=fynmanoj> Ed
Cable <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=edcable>
[image:
Major] Resolved Fixed 04/Aug/20 18/Aug/20
[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-971>
FINERACT-971 <https://issues.apache.org/jira/browse/FINERACT-971>

Activate a few additional recently introduced new Checkstyle rules
<https://issues.apache.org/jira/browse/FINERACT-971>
Manthan Surkar
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Manthan> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger> [image:
Major] Resolved Fixed 10/May/20 17/Aug/20
[image: Sub-task] <https://issues.apache.org/jira/browse/FINERACT-1082>
FINERACT-1082 <https://issues.apache.org/jira/browse/FINERACT-1082>

FINERACT-733 <https://issues.apache.org/jira/browse/FINERACT-733> Automate
Fineract version number population into Swagger doc
<https://issues.apache.org/jira/browse/FINERACT-1082>
Petri Tuomola
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ptuomola> Petri
Tuomola
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ptuomola> [image:
Minor] Resolved Fixed 09/Jul/20 20/Aug/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1118>
FINERACT-1118 <https://issues.apache.org/jira/browse/FINERACT-1118>

Don't run Swagger code generation if previous build steps failed
<https://issues.apache.org/jira/browse/FINERACT-1118>
Petri Tuomola
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ptuomola> Petri
Tuomola
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ptuomola> [image:
Minor] Resolved Fixed 19/Aug/20 20/Aug/20
[image: Improvement] <https://issues.apache.org/jira/browse/FINERACT-1079>
FINERACT-1079 <https://issues.apache.org/jira/browse/FINERACT-1079>

Run Task spotlessApply before commit (Pre-commit)?
<https://issues.apache.org/jira/browse/FINERACT-1079>
Petri Tuomola
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ptuomola> Awasum
Yannick <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=awasum>
[image:
Minor] Resolved Fixed 05/Jul/20 17/Aug/20
[image: Bug] <https://issues.apache.org/jira/browse/FINERACT-1117>
FINERACT-1117 <https://issues.apache.org/jira/browse/FINERACT-1117>

Two Swagger UIs do not work due to wrong parameter type
<https://issues.apache.org/jira/browse/FINERACT-1117>
Petri Tuomola
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ptuomola> Petri
Tuomola
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ptuomola> [image:
Major] Resolved Fixed 15/Aug/20 15/Aug/20
You may edit this subscription here
<https://issues.apache.org/jira/secure/EditSubscription!default.jspa?subId=23124=12349018>.


This message was sent by Atlassian Jira (v8.3.4#803005-sha1:1f96e09)
[image: Atlassian logo]

Re: We are back with more updates on Fineract CN Product

[Michael Vorburger]

I'm not entirely sure what this thread is about.

If this discusses a new project ("Finscale" ?) hosted on
https://github.com/muellners/, then I must join Awasum in expressing
reservations about a non Apache project being discussed on the
dev@fineract.apache.org mailing list.

If this is a discussion about possible future architectural evolution of
the Apache Fineract CN project (despite the linked GDoc stating "Fineract
CN is history and is slowly moving towards extinction." ?), then I guess
it's fine.


On Fri, Aug 21, 2020 at 6:58 PM Saransh Sharma 
wrote:

> Here is the meeting recording for folks who wish to watch the event.
>
>
> https://drive.google.com/file/d/1atM7mG4Nec2fNd9alDWrsOt9Mqqt-FEZ/view?usp=sharing
>
> On Fri, Aug 21, 2020 at 4:06 PM Saransh Sharma 
> wrote:
>
>> Here is the meeting link feel free to join.
>>
>> https://meet.google.com/koa-thmo-abq?authuser=0
>>
>> On Fri, Aug 21, 2020 at 3:43 PM Saransh Sharma 
>> wrote:
>>
>>> Anyone willing to join let me know now, i will add them to the RSVP list.
>>>
>>> Thanks
>>>
>>> On Fri, Aug 21, 2020 at 2:53 PM Ankit Muellner 
>>> wrote:
>>>
 @Awasum,
 I think the relevant Gdoc is a work in progress discussion document
 (something like a pre meeting note or objective discussion notes) not a
 technical wiki document. (This means such a document does not require any
 open source character.)

 There is an OSS usage and delivery policy here
 
  regarding
 this branched project's development, consistent with Apache Fineract
 project.

 We must remember that the current documentation of Fineract requires
 revamp(as is true for any documentation standards) and we should not
 further make these writeups more complicated by adding anything non
 substantial(e.g this Gdoc). This is one suggestion I have for the current
 PMC team and specifically You.
 We must avoid creating a heavy non sequential wiki. I understand we
 have a Lazy consensus in place but for certain key objectives e.g Fineract
 CN upgrade, broader modules etc, this community requires a Workflow for
 addition of write ups to its wiki.

 You are right once the associated documentation for this thread reaches
 maturity, we i.e Muellners should be adding them to Fineract wiki  just
 like everyone else i.e
 https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Home

 Hope this clarifies.


 On Fri, Aug 21, 2020 at 10:48 AM Awasum Yannick <
 yannickawa...@gmail.com> wrote:

> Hi Saransh,
>
>
> On Fri, Aug 21, 2020 at 6:40 AM Saransh Sharma 
> wrote:
>
>> Hey , Devs and Partners
>>
>> We are back with more updates and planning to host yet another
>> session of Fineract CN Updates
>>
>> 1. Last time we discussed product upgrade documentation (Which is in
>> place
>> https://docs.google.com/document/d/1TQox0fQvQexMFj2gX6Si74osKrT5mcIGoYd-mWp3hrc/edit#
>> )
>>
>
> This GDoc is not openly available to everyone. Is this private to your
> company or is it for the Fineract Open Source Community? If we need to
> request for access before viewing the doc then that is not really Open
> Source.
>
> Will you be comfortable sharing your notes on Fineract Wiki:
> https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Home
>
> What libraries have you all upgraded? And have you sent PRs on our
> Apache Fineract CN repos? Or is this something completely private or code
> Open Sourced under your company Org?
>
> 2. Migrating services quicker then before (We might give some
>> walkthrough)
>> 3. We would be focusing on today's call : Migration from Fineract 1.x
>> to CN where we use the existing functional feature in CN.
>>
>
> Is there a repo for the above? Or a PR already opened on Fineract
> repos? Or is this just an idea?
>
>> 4. Developer Perspectives
>> 5. Deployment Scenario
>>
>> Thanks here is the calendar invite join in and lets spread work.
>>
>>
>> https://calendar.google.com/event?action=TEMPLATE=M2Yzb3FjZ3ViazhzYWg3NnFxMzVvM2dhbjEgc2FyYW5zaEBtdWVsbG5lcnMub3Jn=saransh%40muellners.org
>>
>>
>>
> I wonder if we can use the Fineract Wiki available here:
> https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Home to
> document the work we are doing. It will have the docs all in one place and
> not scattered all around.
>
> It will be great if you can record your calls and share with the rest
> of the community who can't attend these calls. This makes it easy for
> people to catch up.
>
>
> Thanks.
> Awasum
>


 --
 Ankit Müllner
 Muellners Europe
 +4581929792

 This mail is governed by 

Re: Fineract 1.4.0 release branch

[Michael Vorburger]

On Wed, Aug 26, 2020 at 12:20 AM Aleksandar Vidakovic <
chee...@monkeysintown.com> wrote:

> Hi Michael,
>
> ... I'm almost there... my release task generates also GPG signatures for
> verification (tested them... all correct).
>

cool!


> Only thing that is left is to include the generated API client JAR; at the
> moment only the sources are created, but no JAR artifact is available. Any
> idea how to proceed here (as this is a release I guess we shouldn't include
> just the client sources)?
>
> All details here: https://issues.apache.org/jira/browse/FINERACT-1129
> (contains also link to sources)
>

I'll engage (and answer above re. client) on that JIRA.


> Cheers
>
> On Tue, Aug 25, 2020 at 9:30 PM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> Alright Michael... the first list it is (WAR, server and client JAR, and
>> README). I'll create a PR for the Gradle task.
>>
>> One more question: I intend to git cherry pick features from develop that
>> arrived after I created the release branch... is that OK or do you guys
>> usually use different approaches (like rebase)?
>>
>
Either is fine with me personally, but I think the real question here is
more another one:

Do you want to cherry-pick very selectively just a limited few particular
last minute changes, or just rebase to catch up with everything on develop.
The latter would in practice really mean that we just branched too soon?
;-) Personally I probably would therefore go for the former (and
cherry-pick, only).

There's always more coming in, and that's fine. Can't stop progress. You
just draw a line in the sand somewhere. There will always be the next
release after. Maybe we can have a 1.5.0 sooner after 1.4.0 than we had
after 1.3.0? :) Otherwise we'll never release... ;-)

A related interesting question is perhaps if YOU (as the RM) should be the
one that raises PR for such cherry-picks. I would argue that you shouldn't
have to... you "did your job" of the process. You've sent the heads up
email, and nobody objected to the timeline you've proposed. Now I
personally would probably just let any contributors who still absolutely
WANT to get anything into 1.4.0 last minute raise PRs for the 1.4.0 branch
themselves (and resolve conflicts, if any; and get them to build).
https://github.com/apache/fineract/pull/1272 was a great working example of
that; as a committer to the project, you can Rebase Merge those yourself in
the future (if they are also on develop; I suggest that we do not put
anything on 1.4.0 that isn't ALREADY in develop; and NOT the other way
around, else it can quickly get very confusing IMHO) .

BTW you could perhaps capture a summary of this discussion / conclusion on
https://cwiki.apache.org/confluence/display/FINERACT/How+to+Release+Apache+Fineract,
if you like.


> On Tue, Aug 25, 2020 at 7:48 PM Michael Vorburger 
>> wrote:
>>
>>> On Tue, 25 Aug 2020, 19:04 Ed Cable,  wrote:
>>>
>>>> Nazeer and Shruthi, are you able to provide some input on this thread
>>>> based on your experiences leading the release process before.
>>>>
>>>> Thanks,
>>>>
>>>> Ed
>>>> On Tue, Aug 25, 2020, 09:45 Aleksandar Vidakovic <
>>>> chee...@monkeysintown.com> wrote:
>>>>
>>>>> Hi Michael,
>>>>>
>>>>> ... I think I saw a release script mentioned somewhere, but don't see
>>>>> it anywhere in the repo.
>>>>>
>>>>> I can put such a release task together for Gradle (aka
>>>>> "distribution")...
>>>>>
>>>>
>>> Yes, that would be really helpful, IMHO! I would be happy to try it out
>>> and peer review a PR from you about this, if you would like.
>>>
>>> that's not too complicated. Just to list the artifacts again:
>>>>>
>>>>>- WAR
>>>>>- server JAR
>>>>>- client JAR
>>>>>
>>>>> SGMT, and let's throw in the /README.md, and whatever else the 1.3.0
>>> dist included?
>>>
>>> How about:
>>>>>
>>>>>- Kubernetes related YAML files
>>>>>
>>>>> I wouldn't, because technically that's not even "1.4.0" - it will pull
>>> :latest from Docker Hub.. we should deal with that "separately & later" (if
>>> ever), IMHO.
>>>
>>>>
>>>>>- should we add maybe add the Docker Compose file so that people
>>>>>can try out Fineract immediately (without installing a separate MySQL
>>>>>instance)
>>>>>

Re: Fineract 1.4.0 release branch

[Michael Vorburger]

On Tue, 25 Aug 2020, 19:04 Ed Cable,  wrote:

> Nazeer and Shruthi, are you able to provide some input on this thread
> based on your experiences leading the release process before.
>
> Thanks,
>
> Ed
> On Tue, Aug 25, 2020, 09:45 Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> Hi Michael,
>>
>> ... I think I saw a release script mentioned somewhere, but don't see it
>> anywhere in the repo.
>>
>> I can put such a release task together for Gradle (aka "distribution")...
>>
>
Yes, that would be really helpful, IMHO! I would be happy to try it out and
peer review a PR from you about this, if you would like.

that's not too complicated. Just to list the artifacts again:
>>
>>- WAR
>>- server JAR
>>- client JAR
>>
>> SGMT, and let's throw in the /README.md, and whatever else the 1.3.0 dist
included?

How about:
>>
>>- Kubernetes related YAML files
>>
>> I wouldn't, because technically that's not even "1.4.0" - it will pull
:latest from Docker Hub.. we should deal with that "separately & later" (if
ever), IMHO.

>
>>- should we add maybe add the Docker Compose file so that people can
>>try out Fineract immediately (without installing a separate MySQL 
>> instance)
>>
>> I also wouldn't, because that won't actually work, because it builds from
source, which won't be in *binary.tar.gz; sorting that out seems like a
separate future task (new JIRA?), to me.

Cheers,
>>
>> Aleks
>>
>> On Tue, Aug 25, 2020 at 4:41 PM Michael Vorburger 
>> wrote:
>>
>>> Aleks, I was struggling to understand how you'll actually be building
>>> the apache-fineract-1.4.0-binary.tar.gz and
>>> apache-fineract-1.3.0-src.tar.gz archives for distribution on
>>> http://fineract.apache.org... I was assuming that we had a script or
>>> (much better) even directly a Gradle task for it in Fineract, but I
>>> couldn't actually find anything like it on git.
>>>
>>>
>>> https://cwiki.apache.org/confluence/display/FINERACT/How+to+Release+Apache+Fineract,
>>> surprisingly, doesn't actually speak to that - or am I just not seeing it?
>>> Hoping someone who was involved in past releases may be able to clarify
>>> here.
>>>
>>> If we never had that, and used to "manually cobble together" these
>>> distributions in the past (huh?), then I think it would be great to see a
>>> PR contributing this. It would be the first step towards more
>>> https://issues.apache.org/jira/browse/FINERACT-876 (later).
>>>
>>> I was looking for it to suggest that we include not only the *.war but
>>> now also the new server *.jar as well as the very recent client *.jar.
>>>
>>> On Tue, Aug 25, 2020 at 9:10 AM Aleksandar Vidakovic <
>>> chee...@monkeysintown.com> wrote:
>>>
>>>> @Ed Cable 
>>>> going through yesterday's emails from Michael et al. to see what recent
>>>> changes have to be included in the 1.4.0 ... had a couple of power outages
>>>> here yesterday. Thanks for the pointers to work that has been done on the
>>>> community app... good to have this on the radar.
>>>>
>>>> Cheers
>>>>
>>>> On Mon, Aug 24, 2020 at 6:52 PM Ed Cable  wrote:
>>>>
>>>>> James,
>>>>>
>>>>> Thanks for bringing up the need for QA. The Mifos Community App UI
>>>>> should be relatively in sync with the Finerat 1.4 changes and I've put the
>>>>> call out for manual QA on Michael's fineract.dev server on the Mifos
>>>>> dev lists since a couple week back at
>>>>>
>>>>> Francis, Bharath, Sangamesh, Chirag, Alex from Habile, and some of our
>>>>> GSOC interns have been involved in the QA thus far at
>>>>> https://discourse.mifos.org/t/pull-request-review-and-qa-for-mifos-x-20-08-release/9671
>>>>>
>>>>> The corresponding tickets at a UI level that complement the Fineract
>>>>> release are being tracked at:
>>>>> https://github.com/openMF/community-app/projects/6 or by following
>>>>> this milestone on Github:
>>>>> https://github.com/openMF/community-app/milestone/1
>>>>>
>>>>> Francis nicely summarized the QA he's done to date in this Google Doc:
>>>>>
>>>>>
>>>>> https://docs.google.com/document/d/1_6kjJxUasLaaZakStDSMKUXw2oqfWt90hzPMuEOFxrE/edit?usp=sharing
>&

Re: Adopting GenerationType.TABLE for ID generation in LoanRepaymentScheduleInstallment entity.

[Michael Vorburger]

On Tue, Aug 25, 2020 at 4:42 PM Yemdjih Kaze Nasser 
wrote:

> Thanks for your input Michael.
>
> I limited my application to the one entity that was most involved with my
> problem. I can bring this out to OPENJPA if it is accepted.
>
> But, please clarify me on one thing. Are you suggesting I apply this for
> all entities as the new generation strategy or just for the
> LoanRepaymentScheduleInstallment entity?
>

Why would we need different ID Generation Strategies for different
Entities? That doesn't make much sense to me, and I fear will only lead to
future confusion.

Why would only the LoanRepaymentScheduleInstallment entity require
a GenerationType.TABLE ID Generation Strategy, but all other Fineract
entities another one? That's... curious. Weird.

I'm kind of reading between the lines that you probably ran into a
particular issue with LoanRepaymentScheduleInstallment during your OpenJPA
to EclipseLink migration. Perhaps whatever caused that could be fixed
differently?


On Tue, Aug 25, 2020, 15:26 Michael Vorburger  wrote:
>
>> On Sun, Aug 23, 2020 at 2:12 PM Yemdjih Kaze Nasser 
>> wrote:
>>
>>> Hello all,
>>>
>>> I have a new strategy I have implemented in EclipseLink migration. I
>>> faced a particular situation where the ID was not generated during the
>>> persistence of an entity causing a lot of SQLIntegrityViolations.
>>> To overcome this, I used GenerationType.TABLE for ID generation on the
>>> entity that faced the most trouble with this
>>> (LoanRepaymentScheduleInstallment entity). For damage control, it's the
>>> only entity that has this change.
>>>
>>> I already have a sample of it on my PR at
>>> https://github.com/apache/fineract/pull/928.
>>>
>>
>> I think this is the kind of thing that would be easiest to review and
>> discuss through a smaller PR proposing to gradually make just that
>> particular change.
>>
>> I'm assuming that it would be technically feasible to use @Id
>> @GeneratedValue(strategy = GenerationType.TABLE) with OpenJPA already as
>> well, like EclipseLink.
>>
>>
>>> It has been tested against the current IT tests we have and it seems to
>>> work fine.
>>>
>>> Now I'd like to get your opinion on this, is this something that will
>>> pose a problem in production, or can we roll with it?
>>>
>>
>> Looking at this
>> <https://github.com/apache/fineract/blob/0b76ffbc83a173eddfbbdf8af038f695e6ce9146/fineract-provider/src/main/java/org/apache/fineract/portfolio/loanaccount/domain/LoanRepaymentScheduleInstallment.java>,
>> my feedback would be that this shouldn't be done like that directly in
>> an @Entity, but EITHER we should have a new AbstractPersistableCustom
>> alternative equivalent (with GenerationType.TABLE), or... just even just
>> change AbstractPersistableCustom directly, really. Because why would we
>> need different ID Generation Strategies for different Entities? That
>> doesn't make much sense, to me, and I fear will only lead to future
>> confusion.
>>
>> BTW if we do do conclude that we want to change this, it would have some
>> interesting data migration implications... ;-(
>>
>> Thanks,
>>> Regards,
>>> Y. K. Nasser
>>>
>>

Re: Fineract 1.4.0 release branch

[Michael Vorburger]

Aleks, I was struggling to understand how you'll actually be building the
apache-fineract-1.4.0-binary.tar.gz and apache-fineract-1.3.0-src.tar.gz
archives for distribution on http://fineract.apache.org... I was assuming
that we had a script or (much better) even directly a Gradle task for it in
Fineract, but I couldn't actually find anything like it on git.

https://cwiki.apache.org/confluence/display/FINERACT/How+to+Release+Apache+Fineract,
surprisingly, doesn't actually speak to that - or am I just not seeing it?
Hoping someone who was involved in past releases may be able to clarify
here.

If we never had that, and used to "manually cobble together" these
distributions in the past (huh?), then I think it would be great to see a
PR contributing this. It would be the first step towards more
https://issues.apache.org/jira/browse/FINERACT-876 (later).

I was looking for it to suggest that we include not only the *.war but now
also the new server *.jar as well as the very recent client *.jar.

On Tue, Aug 25, 2020 at 9:10 AM Aleksandar Vidakovic <
chee...@monkeysintown.com> wrote:

> @Ed Cable 
> going through yesterday's emails from Michael et al. to see what recent
> changes have to be included in the 1.4.0 ... had a couple of power outages
> here yesterday. Thanks for the pointers to work that has been done on the
> community app... good to have this on the radar.
>
> Cheers
>
> On Mon, Aug 24, 2020 at 6:52 PM Ed Cable  wrote:
>
>> James,
>>
>> Thanks for bringing up the need for QA. The Mifos Community App UI should
>> be relatively in sync with the Finerat 1.4 changes and I've put the call
>> out for manual QA on Michael's fineract.dev server on the Mifos dev
>> lists since a couple week back at
>>
>> Francis, Bharath, Sangamesh, Chirag, Alex from Habile, and some of our
>> GSOC interns have been involved in the QA thus far at
>> https://discourse.mifos.org/t/pull-request-review-and-qa-for-mifos-x-20-08-release/9671
>>
>> The corresponding tickets at a UI level that complement the Fineract
>> release are being tracked at:
>> https://github.com/openMF/community-app/projects/6 or by following this
>> milestone on Github: https://github.com/openMF/community-app/milestone/1
>>
>> Francis nicely summarized the QA he's done to date in this Google Doc:
>>
>>
>> https://docs.google.com/document/d/1_6kjJxUasLaaZakStDSMKUXw2oqfWt90hzPMuEOFxrE/edit?usp=sharing
>>
>> @Aleksandar Vidakovic  Thank you again for
>> taking up the role of release manager. I do think that although it would
>> push the release out a couple more days we should continue doing some
>> remaining manual QA this week. There are also two important tickets that
>> Avik from Fynarfin is aiming to have fixes for by Thursday to go into this
>> release: https://issues.apache.org/jira/browse/FINERACT-629 and
>> https://issues.apache.org/jira/browse/FINERACT-1120
>>
>> With the release branch available, we're deploying it locally to some
>> users as well who are testing it in their development environments.
>>
>> Ed
>>
>> On Sun, Aug 23, 2020 at 1:00 PM Aleksandar Vidakovic <
>> chee...@monkeysintown.com> wrote:
>>
>>> I've added a note on
>>> https://cwiki.apache.org/confluence/display/FINERACT/How+to+Release+Apache+Fineract
>>> about the manual testing. FYI
>>>
>>> On Fri, Aug 21, 2020 at 7:52 PM Aleksandar Vidakovic <
>>> chee...@monkeysintown.com> wrote:
>>>
 Hi James,

 ... alright... noted. A bit new to the release game here so the
 requirement to manually test slipped through the cracks. But maybe August
 might also not be the best of months for a release; responses to the
 various release announcements on the mailing list were a bit scarce.

 Having said that: someone wants to help out with QA as James mentioned?
 I'll give it a run on my machine, but would be great if we get a couple
 more people to verify.

 Speaking of manual testing - maybe we could do this a bit less
 manual... I wanted to propose this already for a while and didn't get to
 it: https://gatling.io/

 So technically Gatling is a load testing tool, but it has a feature
 called Gatling Recorder (https://gatling.io/docs/current/http/recorder/)
 that allows you to record all interaction between browser (read: community
 app) and Fineract. That way we could get those test scenarios once recorded
 and just include them in the build as some kind of integration test. The
 beauty of this is that maintenance doesn't require any coding, just run a
 specific scenario again in your browser; could even replace the current
 integration tests in Fineract that should - I guess - cover more or less UI
 scenarios, but are currently a bit neglected.

 Please ping here on the list if you want to help out. We can coordinate
 then for the final release date (I guess that won't be Monday).

 Thanks again for the help James.

 Cheers,

 Aleks

 On Fri, Aug 21,