[
https://issues.apache.org/jira/browse/FINERACT-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18134213#comment-18134213
]
Sonigra Bhavya Hemendrabhai commented on FINERACT-3020:
-------------------------------------------------------
this pr: https://github.com/apache/fineract/pull/6783 has solved the issue.
> SavingsAccountRepositoryWrapperLockOrderTest fails to compile on develop due
> to missing PlatformSecurityContext argument
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: FINERACT-3020
> URL: https://issues.apache.org/jira/browse/FINERACT-3020
> Project: Apache Fineract
> Issue Type: Bug
> Components: Savings
> Affects Versions: 1.16.0
> Reporter: Sonigra Bhavya Hemendrabhai
> Assignee: Sonigra Bhavya Hemendrabhai
> Priority: Blocker
> Fix For: 1.16.0
>
>
> After the merge of FINERACT-2639 (PR #6698), a PlatformSecurityContext
> parameter was added to the SavingsAccountRepositoryWrapper constructor.
> However, SavingsAccountRepositoryWrapperLockOrderTest (merged from PR #6591)
> uses the old 2-argument constructor.
> As a result, develop currently fails during :fineract-savings:compileTestJava
> with:
> SavingsAccountRepositoryWrapperLockOrderTest.java:36: error: constructor
> SavingsAccountRepositoryWrapper in class SavingsAccountRepositoryWrapper
> cannot be applied to given types;
> private final SavingsAccountRepositoryWrapper underTest = new
> SavingsAccountRepositoryWrapper(repository,
> ^
> required:
> SavingsAccountRepository,SavingsAccountTransactionRepository,PlatformSecurityContext
> found: SavingsAccountRepository,SavingsAccountTransactionRepository
> reason: actual and formal argument lists differ in length
> Fix:
> Pass mock(PlatformSecurityContext.class) to the
> SavingsAccountRepositoryWrapper constructor in
> SavingsAccountRepositoryWrapperLockOrderTest.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
