Kapil, I was seeing some similar-looking problems trying to run integration tests locally.
I was able to get my tests running again following some of the extra clean-up procedures documented in https://github.com/apache/fineract#integration-tests , specifically: git clean --force -dx rm -rf ~/.gradle ~/.m2 /tmp/cargo* I notice you mentioned in chat that you also got your build working again, so that's great. 👍 (would-be copy-pasters please note those commands above can blow away GiB of useful cache as well as IDE settings) Best, -Adam Monsen On Mon, Sep 8, 2025 at 5:44 AM Ádám Sághy <[email protected]> wrote: > Hi Kapi, > > Unfortunately the shared piece of stacktrace of your console log does not > help to identify the issue. I am afraid I need the FULL console log to > advise on the potential problem. > > If you dont want to share it with the rest of the world, feel free to > reach out to me privately on the [email protected] > > In the meantime some things to be considered: > > Running `./gradlew :fineract-provider:build` would not just build the > project, but it tries to run the integration tests and E2E tests, generate > fineract-docs, etc. > > if you need to run the application for development purposes, please run > this instead: `./gradlew bootRun` > > If you need a bootable jar, please run this instead: `./gradlew bootJar` > -> Good for building a fatJar which set up Spring Boot running environment. > > if you need a build the project (fineract-client, jar, etc.), BUT no need > to run integration tests and E2E tests, please use: `./gradlew --no-daemon > build -x test -x cucumber -x doc` > > I hope it helps! > > Regards, > Adam > > On 2025. Sep 8., at 9:36, Kapil Panchal < > [email protected]> wrote: > > Hi Adam, > > I am building it on my system and this is the stack trace, run the > command ./gradlew --refresh-dependencies :fineract-provider:build > or ./gradlew fineract-provider:cucumber > > 2025-09-08 13:00:44.961 [main] WARN > o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker - Bean > 'samplingConfiguration' of type > [org.apache.fineract.infrastructure.core.diagnostics.performance.sampling.core.SamplingConfiguration] > is not eligible for getting processed by all BeanPostProcessors (for > example: not eligible for auto-proxying). Is this bean getting eagerly > injected/applied to a currently created BeanPostProcessor > [samplingBeanPostProcessor]? Check the corresponding BeanPostProcessor > declaration and its dependencies/advisors. If this bean does not have to be > post-processed, declare it with ROLE_INFRASTRUCTURE. > >
