[jira] [Assigned] (FINERACT-1079) Run Task spotlessApply before compileJava?
[ https://issues.apache.org/jira/browse/FINERACT-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser reassigned FINERACT-1079: - Assignee: Awasum Yannick > Run Task spotlessApply before compileJava? > -- > > Key: FINERACT-1079 > URL: https://issues.apache.org/jira/browse/FINERACT-1079 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Awasum Yannick >Assignee: Awasum Yannick >Priority: Minor > Fix For: 1.4.0 > > > Developers consistently have problems manually running the spotlessApply task > after coding changes... See: [https://github.com/apache/fineract/pull/1151] > and [https://github.com/apache/fineract/pull/1148] > maybe we should just run spotlessApply just before compilation and skip the > tasks to check for spotless failures? Or we run both of them: Run > spotlessApply before spotlessCheck (seems wasteful). Is this a good idea? I > wonder? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1079) Run Task spotlessApply before compileJava?
[ https://issues.apache.org/jira/browse/FINERACT-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser resolved FINERACT-1079. --- Resolution: Fixed > Run Task spotlessApply before compileJava? > -- > > Key: FINERACT-1079 > URL: https://issues.apache.org/jira/browse/FINERACT-1079 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Awasum Yannick >Assignee: Awasum Yannick >Priority: Minor > Fix For: 1.4.0 > > > Developers consistently have problems manually running the spotlessApply task > after coding changes... See: [https://github.com/apache/fineract/pull/1151] > and [https://github.com/apache/fineract/pull/1148] > maybe we should just run spotlessApply just before compilation and skip the > tasks to check for spotless failures? Or we run both of them: Run > spotlessApply before spotlessCheck (seems wasteful). Is this a good idea? I > wonder? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINERACT-1079) Run Task spotlessApply before compileJava?
Awasum Yannick created FINERACT-1079: Summary: Run Task spotlessApply before compileJava? Key: FINERACT-1079 URL: https://issues.apache.org/jira/browse/FINERACT-1079 Project: Apache Fineract Issue Type: Improvement Reporter: Awasum Yannick Fix For: 1.4.0 Developers consistently have problems manually running the spotlessApply task after coding changes... See: [https://github.com/apache/fineract/pull/1151] and [https://github.com/apache/fineract/pull/1148] maybe we should just run spotlessApply just before compilation and skip the tasks to check for spotless failures? Or we run both of them: Run spotlessApply before spotlessCheck (seems wasteful). Is this a good idea? I wonder? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1054) Error at Loan Repayments
[ https://issues.apache.org/jira/browse/FINERACT-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17151540#comment-17151540 ] Francis Guchie commented on FINERACT-1054: -- I am having challenges with all my PRs > Error at Loan Repayments > > > Key: FINERACT-1054 > URL: https://issues.apache.org/jira/browse/FINERACT-1054 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Priority: Critical > Labels: beginner > > GET > https:///fineract-provider/api/v1/loans/3/transactions/template?command=repayment > > timestamp 1592952834187 > status500 > error "Internal Server Error" > message "PreparedStatementCallback; bad SQL grammar [select > if(max(tr.transaction_date)>ls.dueDate,max(tr.transaction_date),ls.dueDate) > as transactionDate,ls.principal_amount - > IFNULL(ls.principal_writtenoff_derived,0) - > IFNULL(ls.principal_completed_derived,0) as principalDue,ls.interest_amount - > IFNULL(ls.interest_completed_derived,0) - > IFNULL(ls.interest_waived_derived,0) - > IFNULL(ls.interest_writtenoff_derived,0) as interestDue,ls.fee_charges_amount > - IFNULL(ls.fee_charges_completed_derived,0) - IFNULL(ls.fee_c…N ls.loan_id = > l.id AND ls.completed_derived = 0 join( (select min(ls.duedate) > datedue,ls.loan_id from m_loan_repayment_schedule ls where ls.loan_id = ? and > ls.completed_derived = 0) )asq on asq.loan_id = ls.loan_id and asq.datedue = > ls.duedate where l.id =?]; nested exception is > java.sql.SQLSyntaxErrorException: In aggregated query without GROUP BY, > expression #2 of SELECT list contains nonaggregated column > 'fineract_default.ls.principal_amount'; this is incompatible with > sql_mode=only_full_group_by" > path "/fineract-provider/api/v1/loans/3/transactions/template" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-232) Ability to Post General Ledger Entries Directly to Customer Account
[ https://issues.apache.org/jira/browse/FINERACT-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-232: Labels: functional gsoc large (was: Fineract-CN gsoc large p3) > Ability to Post General Ledger Entries Directly to Customer Account > --- > > Key: FINERACT-232 > URL: https://issues.apache.org/jira/browse/FINERACT-232 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting, Loan, Savings >Reporter: Dayna Harp >Priority: Major > Labels: functional, gsoc, large > Attachments: Complete New UI Mock up for Journal Entry Screen.png, > Enhancements for Journal Entry.pdf > > > https://mifosforge.jira.com/browse/MIFOSX-2182 > From MIFOS X: As an accountant, i would like to be able to make a transfer > from a client's account (Savings Account or Loan Account) to a GL Account and > also be able to make transfer from a GL Account (e.g Cash at Hand) to > Client's Account (e.g Savings Account or Loan Account) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-232) Ability to Post General Ledger Entries Directly to Customer Account
[ https://issues.apache.org/jira/browse/FINERACT-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-232: Component/s: Savings Loan > Ability to Post General Ledger Entries Directly to Customer Account > --- > > Key: FINERACT-232 > URL: https://issues.apache.org/jira/browse/FINERACT-232 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting, Loan, Savings >Reporter: Dayna Harp >Priority: Major > Labels: Fineract-CN, gsoc, large, p3 > Attachments: Complete New UI Mock up for Journal Entry Screen.png, > Enhancements for Journal Entry.pdf > > > https://mifosforge.jira.com/browse/MIFOSX-2182 > From MIFOS X: As an accountant, i would like to be able to make a transfer > from a client's account (Savings Account or Loan Account) to a GL Account and > also be able to make transfer from a GL Account (e.g Cash at Hand) to > Client's Account (e.g Savings Account or Loan Account) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-1077) Migrate from legacy plugins applications to plugins DSL in build.gradle
[ https://issues.apache.org/jira/browse/FINERACT-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser reassigned FINERACT-1077: - Assignee: Yemdjih Kaze Nasser > Migrate from legacy plugins applications to plugins DSL in build.gradle > --- > > Key: FINERACT-1077 > URL: https://issues.apache.org/jira/browse/FINERACT-1077 > Project: Apache Fineract > Issue Type: Improvement > Components: Build >Affects Versions: 1.4.0 >Reporter: Yemdjih Kaze Nasser >Assignee: Yemdjih Kaze Nasser >Priority: Major > > We are still using the old way of applying gradle plugins in our > build.gradle. Today there is more convenient way of doing this which more and > more packages are using. This would make the build less cumbersome too and > plugins easier to maintain and apply. > [https://docs.gradle.org/current/userguide/plugins.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
