Re: Error: Cannot add task 'integrationTest' as a task with that name already exists.

[Vishwas Babu]

Mua,

Regarding https://github.com/flyway/flyway/issues/2332

The issue isn't strictly related to the version of the MySQL server, rather
the driver used. Please provide any other relevant information that would
help the Flyway folks determine the root cause. At the minimum
-> Mention that you do not get this issue with MySQL connector, MariaDB
driver etc and are only facing the issue with drizzle driver (version
details etc)
-> Mention that the same worked with a previous version of Flyway (version
X.X) and broke after you upgraded to this version.

Since this would most likely be a very low priority issue for Flyway, they
might not provide a fix for the same. However, you could ask them to help
you identify the section of the codebase which is throwing the error and
possibly make a fix yourself.

>> would love to take up another issue if permitted as the response from
the flyway team may slow me down
Of course, please feel free to pick up any issue that interests you :)

Some issues
- > https://jira.apache.org/jira/browse/FINERACT-728
- > https://jira.apache.org/jira/browse/FINERACT-726


Regards,
Vishwas



On Wed, Mar 20, 2019 at 7:30 PM Mua Rachmann  wrote:

> Hi Vishwas,
>
> Thanks for your reply. I used mysql-connector in my PR here and it works
> fine but seems to be GPL licence which is not
> compatible with ASF. From all indications the flyway tasks will fail if
> gradle is upgraded.
>
> I did as you said and filed an issue on the flyway repo here -
> https://github.com/flyway/flyway/issues/2332
> They replied and i hope a solution will spring forth.
>
> As for the mysql-connector driver. All i have come across is not compatible
> with ASF licence. I am still
> searching though.
>
> I would love to take up another issue if permitted as the response from the
> flyway team may slow me down
>
> All issues i have taken so far depends on gradle to be upgraded that is
> why.
>
> Regards Mua
>
> On Tue, Mar 19, 2019 at 11:03 PM Vishwas Babu <
> vish...@confluxtechnologies.com> wrote:
>
> > Hi Mua,
> >
> > This topic was discussed earlier at
> >
> >
> https://lists.apache.org/thread.html/2d84501386e0479e9016e3c6cbbaafbcea0aa1afdff6f19caadc8658@%3Cdev.fineract.apache.org%3E
> > .
> >
> > Here's the relevant snippet with details of alternatives for
> > TaskInternal.execute()
> >
> > Details of a quick fix I attempted to work around the removed
> > TaskInternal.execute() method follow.
> >
> > Using finalizedBy instead of execute ( i.e
> migrateTenantListDB.finalizedBy
> > flywayMigrate) led to the error "Could not get unknown property
> > 'classesDir' for integration test classes of type
> > org.gradle.api.internal.tasks.DefaultSourceSetOutput". This was fixed by
> > upgrading flyway plugin to.
> >
> > apply plugin: 'org.flywaydb.flyway'
> > dependencies {
> > classpath
> > "gradle.plugin.com.boxfuse.client:gradle-plugin-publishing:5.2.4"
> > }
> > }
> >
> > However, this does not seem to work with the current drizzle driver on
> the
> > classpath (results in the error "MySQL upgrade required: MySQL 0.1 is
> > outdated and no longer supported by Flyway. Flyway currently supports
> MySQL
> > 5.1 and newer"). It runs without issues if I swap in a MySQL driver
> though.
> >
> >
> > So, the work for completing the gradle upgrade is blocked due to the
> issue
> > with the drizzle driver (at
> > https://github.com/krummas/DrizzleJDBC/blob/master/LICENSE.txt), which
> is
> > no longer maintained.  We cannot change the driver to MySQL connector etc
> > due to licensing issues (GPL v2 used by the driver is not compatible with
> > the Apache license). The other popular alternative i.e MariaDB connector
> > uses an LGPL license, is also not compatible with Apache license.
> >
> > Here are some things we could explore
> >
> > -> Raise an issue with https://github.com/flyway/flyway and explore the
> > fix
> > needed to be made for this error i.e "MySQL upgrade required: MySQL 0.1
> is
> > outdated and no longer supported by Flyway. Flyway currently supports
> MySQL
> > 5.1 and newer" when using Drizzle driver.
> > This error message seems wrong since the MySQL version we are using is
> > greater than 5.1
> > -> (Long term solution) Find another MySQL driver using a permitted
> licence
> > (BSD , MIT etc. permitted licenses at
> > https://www.apache.org/legal/resolved.html#category-a)
> >
> > Regards,
> > Vishwas
> >
> > On Mon, Mar 18, 2019 at 7:38 AM Mua Rachmann 
> > wrote:
> >
> > > Hello everyone,
> > >
> > > Trust you are all well. I have been working on MIcheal's PR to upgrade
> > the
> > > gradle to 5.2.1 here - https://github.com/apache/fineract/pull/525
> > >
> > > Currently I upgraded the flyway plugin of which i found a compatible
> > mysql
> > > connector (mysql-connector 8.0.12) which makes it possible to migrate
> the
> > > sql files with some few warnings of which i handled in the PR. see
> here -
> > > https://github.com/apache/fineract/pull/550
> > >
> > > For some reasons I don't know why the 

Re: Need help moving to the next step

[Mauricio Ghiorzi]

Hello Adam,

Do you follow the guide on the wiki?
https://mifosforge.jira.com/wiki/spaces/MDZ/pages/93093939/Eclipse+Setup

Regards



[image: Imágenes integradas 2]


*Mauricio Ghiorzi -  Lead Technology Specialist *Av. del Libertador 2442,
Piso 2, CP 1636, Olivos
Buenos Aires, Argentina -  Tel.: +54911 5046 6624

www.wenance.com



El mié., 20 mar. 2019 a las 20:35, Amin Adam ()
escribió:

> Hi everyone. So far I have managed to successfully built and run both the
> mifos community web app and the fineract platform on the local server.
>
> Next I would like to know how to setup the projects on an ide like eclipse
> of visual studio code to start programming and testing the changes i make.
>
> Can someone point me to a a thread that has this discussion or a page where
> it outlines the steps to do so.
>
> Thank you in advance.
>

Re: Error: Cannot add task 'integrationTest' as a task with that name already exists.

[Mua Rachmann]

Hi Vishwas,

Thanks for your reply. I used mysql-connector in my PR here and it works
fine but seems to be GPL licence which is not
compatible with ASF. From all indications the flyway tasks will fail if
gradle is upgraded.

I did as you said and filed an issue on the flyway repo here -
https://github.com/flyway/flyway/issues/2332
They replied and i hope a solution will spring forth.

As for the mysql-connector driver. All i have come across is not compatible
with ASF licence. I am still
searching though.

I would love to take up another issue if permitted as the response from the
flyway team may slow me down

All issues i have taken so far depends on gradle to be upgraded that is why.

Regards Mua

On Tue, Mar 19, 2019 at 11:03 PM Vishwas Babu <
vish...@confluxtechnologies.com> wrote:

> Hi Mua,
>
> This topic was discussed earlier at
>
> https://lists.apache.org/thread.html/2d84501386e0479e9016e3c6cbbaafbcea0aa1afdff6f19caadc8658@%3Cdev.fineract.apache.org%3E
> .
>
> Here's the relevant snippet with details of alternatives for
> TaskInternal.execute()
>
> Details of a quick fix I attempted to work around the removed
> TaskInternal.execute() method follow.
>
> Using finalizedBy instead of execute ( i.e migrateTenantListDB.finalizedBy
> flywayMigrate) led to the error "Could not get unknown property
> 'classesDir' for integration test classes of type
> org.gradle.api.internal.tasks.DefaultSourceSetOutput". This was fixed by
> upgrading flyway plugin to.
>
> apply plugin: 'org.flywaydb.flyway'
> dependencies {
> classpath
> "gradle.plugin.com.boxfuse.client:gradle-plugin-publishing:5.2.4"
> }
> }
>
> However, this does not seem to work with the current drizzle driver on the
> classpath (results in the error "MySQL upgrade required: MySQL 0.1 is
> outdated and no longer supported by Flyway. Flyway currently supports MySQL
> 5.1 and newer"). It runs without issues if I swap in a MySQL driver though.
>
>
> So, the work for completing the gradle upgrade is blocked due to the issue
> with the drizzle driver (at
> https://github.com/krummas/DrizzleJDBC/blob/master/LICENSE.txt), which is
> no longer maintained.  We cannot change the driver to MySQL connector etc
> due to licensing issues (GPL v2 used by the driver is not compatible with
> the Apache license). The other popular alternative i.e MariaDB connector
> uses an LGPL license, is also not compatible with Apache license.
>
> Here are some things we could explore
>
> -> Raise an issue with https://github.com/flyway/flyway and explore the
> fix
> needed to be made for this error i.e "MySQL upgrade required: MySQL 0.1 is
> outdated and no longer supported by Flyway. Flyway currently supports MySQL
> 5.1 and newer" when using Drizzle driver.
> This error message seems wrong since the MySQL version we are using is
> greater than 5.1
> -> (Long term solution) Find another MySQL driver using a permitted licence
> (BSD , MIT etc. permitted licenses at
> https://www.apache.org/legal/resolved.html#category-a)
>
> Regards,
> Vishwas
>
> On Mon, Mar 18, 2019 at 7:38 AM Mua Rachmann 
> wrote:
>
> > Hello everyone,
> >
> > Trust you are all well. I have been working on MIcheal's PR to upgrade
> the
> > gradle to 5.2.1 here - https://github.com/apache/fineract/pull/525
> >
> > Currently I upgraded the flyway plugin of which i found a compatible
> mysql
> > connector (mysql-connector 8.0.12) which makes it possible to migrate the
> > sql files with some few warnings of which i handled in the PR. see here -
> > https://github.com/apache/fineract/pull/550
> >
> > For some reasons I don't know why the migrations perform the same
> stuffs.I
> > would love for someone to please review and tell me what i am doing
> wrong.
> >
> > Also due to the execute() method being removed in gradle 5. I keep on
> > getting this error when i run any command like ./gradlew flywayMigrate,
> > ./gradlew tomcatRunWar. See sample here - https://pastebin.com/VfyGXG9j
> >
> > I would love to know how to make the default execute() functions in the
> > build.gradle file work thanks
> >
> > Best regards, Mua
> >
>

Re: Not able to define interest rate chart

[Subramanya M K]

Thank you very much, for the quick response, Santosh.

With respect to the new version release...is it planned in near future? or
do you suggest us to go ahead with previous version for the time-being?

Thanks and Regards,
Subramanya

On Wed 20 Mar, 2019, 19:45 Santosh Math  Hi Subramanya,
> The drop downs are related to "Manage Codes" . Go to System , then Manage
> Codes and search for required code , ex: Gender and then add the values.
>
> On Wed 20 Mar, 2019, 7:38 PM Subramanya M K,  wrote:
>
>> Hi Santosh,
>>
>> In continuation of the mails above, while creating the customers /
>> clients few drop down fields like "Gender" , "Type" etc are coming blank.
>> Are these maintainable "List of Values" or are they factory shipped
>> values?
>> We have re-installed this latest version of mifos X (i.e. 18.03) with
>> mysql 5.6 version post discussion with you in the above mails.
>> The society where we want to use this version is going to start its
>> operations from April 2019. So, just wanted to check with you, are there
>> any plans of new version release with issues reported fixed before April
>> 2019 or should we go ahead and re-install the previous version?
>> Request your help / suggestion in this regard at the earliest.
>>
>> Thanks and Regards,
>> Subramanya
>>
>> On Thu, Jan 17, 2019 at 5:25 PM Santosh Math <
>> sant...@confluxtechnologies.com> wrote:
>>
>>> You can track here :
>>>
>>> https://github.com/openMF/community-app/projects/6
>>>
>>> We have around 36 tickets which need to be resolved. Once they resolved,
>>> next version Mifos will be ready for release.
>>>
>>> On Thu, Jan 17, 2019 at 5:18 PM Subramanya M K 
>>> wrote:
>>>
 Thank you very much, Santosh.

 @Santosh - kindly let us know by when the next release will be done, so
 that we can plan accordingly.

 @Vinay - please check if we can wait till the next release (if it is
 scheduled shortly) and then install.

 Thanks and regards,
 Subramanya

 On Thu 17 Jan, 2019, 17:00 Santosh Math <
 sant...@confluxtechnologies.com wrote:

> Hi Subramanya,
>
> The issue is fixed and will be available with next MIfos release. You
> can test in the staging environment, https://staging.openmf.org which
> has the latest code yet to be released.
>
> On Thu, Jan 17, 2019 at 2:50 PM Subramanya M K 
> wrote:
>
>> Thank you, Santosh.
>>
>> Just wanted to bring to your notice that we had installed the
>> mentioned version. However, the issues what is discussed above were 
>> found.
>> I hope the above discussed issues are fixed now in the same version
>> and we can go ahead reinstalling the same.
>> Thanking you and awaiting your response to go ahead with the
>> installation.
>>
>> Thanks and regards,
>> Subramanya
>>
>> On 17-Jan-2019 7:20 AM, "Santosh Math" <
>> sant...@confluxtechnologies.com> wrote:
>>
>> Hi Vinay,
>>
>> Sorry for delayed reply. The latest released version is 18.03.01 and
>> sooner we're going to release next version. You can download released
>> version from this link.
>>
>> https://sourceforge.net/projects/mifos/
>>
>> Installationg Guide:
>>
>> https://mifosforge.jira.com/wiki/spaces/docs/pages/53215236/Mifos+X+Installation+on+Windows
>>
>> On Fri, Jan 11, 2019 at 10:53 PM vinay bhat 
>> wrote:
>>
>>> Hi Santosh,
>>>
>>> Many thanks for your reply.
>>>
>>> We would like to implement latest version from mifos. Mifos.org
>>> routes us to  *MIFOS X 18.03.01* community app. So kindly guide
>>> which version to be installed along with it's download link.
>>>
>>> Many thanks in advance.
>>>
>>> Thanks & Regards,
>>> Vinay
>>>
>>>
>>> On Fri, Jan 11, 2019 at 9:33 PM Myrle Krantz 
>>> wrote:
>>>
 (removed dev@community, and dev@fineract. added private@fineract,
 and Vishwas)

 Fineract people: dev@community has a huge recipient list and only
 a small portion of them are interested in financial inclusion.  I've 
 asked
 twice already, to stop sending Fineract specific e-mails to that list. 
  If
 you keep it up, you may land on a rather large number of people's email
 filter list.  You may also damage our project's reputation at Apache.

 When you send emails to a large number of people you need to always
 make sure that you know who you are sending to, and what the purpose of
 your email is and to make sure that these two match.  Don't just hit 
 reply
 all.

 Best Regards,
 Myrle

 On Wed, Jan 2, 2019 at 9:00 AM Subramanya M K 
 wrote:

> Thank you very much, Santosh.
>
> Thanks and regards,
> Subramanya
>
> On Wed 2 Jan, 2019, 11:35 

Re: Not able to define interest rate chart

[Santosh Math]

Hi Subramanya,
The drop downs are related to "Manage Codes" . Go to System , then Manage
Codes and search for required code , ex: Gender and then add the values.

On Wed 20 Mar, 2019, 7:38 PM Subramanya M K,  wrote:

> Hi Santosh,
>
> In continuation of the mails above, while creating the customers / clients
> few drop down fields like "Gender" , "Type" etc are coming blank.
> Are these maintainable "List of Values" or are they factory shipped values?
> We have re-installed this latest version of mifos X (i.e. 18.03) with
> mysql 5.6 version post discussion with you in the above mails.
> The society where we want to use this version is going to start its
> operations from April 2019. So, just wanted to check with you, are there
> any plans of new version release with issues reported fixed before April
> 2019 or should we go ahead and re-install the previous version?
> Request your help / suggestion in this regard at the earliest.
>
> Thanks and Regards,
> Subramanya
>
> On Thu, Jan 17, 2019 at 5:25 PM Santosh Math <
> sant...@confluxtechnologies.com> wrote:
>
>> You can track here :
>>
>> https://github.com/openMF/community-app/projects/6
>>
>> We have around 36 tickets which need to be resolved. Once they resolved,
>> next version Mifos will be ready for release.
>>
>> On Thu, Jan 17, 2019 at 5:18 PM Subramanya M K 
>> wrote:
>>
>>> Thank you very much, Santosh.
>>>
>>> @Santosh - kindly let us know by when the next release will be done, so
>>> that we can plan accordingly.
>>>
>>> @Vinay - please check if we can wait till the next release (if it is
>>> scheduled shortly) and then install.
>>>
>>> Thanks and regards,
>>> Subramanya
>>>
>>> On Thu 17 Jan, 2019, 17:00 Santosh Math >> wrote:
>>>
 Hi Subramanya,

 The issue is fixed and will be available with next MIfos release. You
 can test in the staging environment, https://staging.openmf.org which
 has the latest code yet to be released.

 On Thu, Jan 17, 2019 at 2:50 PM Subramanya M K 
 wrote:

> Thank you, Santosh.
>
> Just wanted to bring to your notice that we had installed the
> mentioned version. However, the issues what is discussed above were found.
> I hope the above discussed issues are fixed now in the same version
> and we can go ahead reinstalling the same.
> Thanking you and awaiting your response to go ahead with the
> installation.
>
> Thanks and regards,
> Subramanya
>
> On 17-Jan-2019 7:20 AM, "Santosh Math" <
> sant...@confluxtechnologies.com> wrote:
>
> Hi Vinay,
>
> Sorry for delayed reply. The latest released version is 18.03.01 and
> sooner we're going to release next version. You can download released
> version from this link.
>
> https://sourceforge.net/projects/mifos/
>
> Installationg Guide:
>
> https://mifosforge.jira.com/wiki/spaces/docs/pages/53215236/Mifos+X+Installation+on+Windows
>
> On Fri, Jan 11, 2019 at 10:53 PM vinay bhat 
> wrote:
>
>> Hi Santosh,
>>
>> Many thanks for your reply.
>>
>> We would like to implement latest version from mifos. Mifos.org
>> routes us to  *MIFOS X 18.03.01* community app. So kindly guide
>> which version to be installed along with it's download link.
>>
>> Many thanks in advance.
>>
>> Thanks & Regards,
>> Vinay
>>
>>
>> On Fri, Jan 11, 2019 at 9:33 PM Myrle Krantz 
>> wrote:
>>
>>> (removed dev@community, and dev@fineract. added private@fineract,
>>> and Vishwas)
>>>
>>> Fineract people: dev@community has a huge recipient list and only a
>>> small portion of them are interested in financial inclusion.  I've asked
>>> twice already, to stop sending Fineract specific e-mails to that list.  
>>> If
>>> you keep it up, you may land on a rather large number of people's email
>>> filter list.  You may also damage our project's reputation at Apache.
>>>
>>> When you send emails to a large number of people you need to always
>>> make sure that you know who you are sending to, and what the purpose of
>>> your email is and to make sure that these two match.  Don't just hit 
>>> reply
>>> all.
>>>
>>> Best Regards,
>>> Myrle
>>>
>>> On Wed, Jan 2, 2019 at 9:00 AM Subramanya M K 
>>> wrote:
>>>
 Thank you very much, Santosh.

 Thanks and regards,
 Subramanya

 On Wed 2 Jan, 2019, 11:35 Santosh Math <
 sant...@confluxtechnologies.com
 wrote:

 > Hi Subramanya,
 > It was the issue of last release 18.03 which is raised here and
 fixed.
 > https://github.com/openMF/community-app/issues/2942
 >
 > You can test the bug fixes/improvements of the upcoming release
 in the
 > following instance.
 >
 > https://staging.openmf.org/#/n  (mifos/password)

Re: Closing Issues when they have been rectified

[Santosh Math]

Hi Fon,

The tickets are closed only after testing, not after PR is sent or merged.
I think most of the tickets are tested and closed after PR is merged. If
the ticket is open even after PR merge, it means the issue is not yet
resolved.



On Mon, Mar 18, 2019 at 1:15 PM Fon Lawrence 
wrote:

> Hi Wonderful people,
>
> Hope we are all waxing strong. I have a problem which I hoped we could
> correct.
>
> while going through the community app issues on
> https://github.com/openMF/community-app/issues/ I noticed that many issues
> that have already been rectified are still labeled open. I just hope we
> could look into that cause it makes finding an actual open issue more
> difficult.
>
> Hope we all look into this to make our community more friendly to those who
> are just joining us.
>
> Thanks,
> Lawrence.
>


-- 
Thanks & Regards

Santosh Math

*QA Engineer*

*Conflux Technologies Pvt Ltd *
| *Office*: +91-080-41208662 |

*Address*: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block,
Bengaluru, Karnataka, 560043 INDIA