Hello Michael ! Thank you, it was gradle daemon issue. I use Intellig Idea and this IDE works with gradle daemon by default.
I have one more question: Is there any reason for old version of tomcat in dev dependencies? def tomcatVersion = '7.0.54' while in prod def tomcatVersion = '7.0.94' It is really interesting for me to help you with gradle-tomcat-plugin. How can I join to you in this work? Best regards, Ivan вт, 1 окт. 2019 г. в 19:08, Michael Vorburger <[email protected]>: > On Tue, 1 Oct 2019, 17:58 Ivan Bondarenko, <[email protected]> wrote: > >> Hello! >> >> I'm trying to run integration tests locally. >> And first time it fails on awaitSpringBootActuatorHealthyUp() >> "/fineract-provider/health" returns 404. >> > > You should check the log to see why.. > > Next times tomcat fail to start with error: >> *Caused by: java.lang.IllegalStateException: Illegal class loader binding* >> >> (Full stack in attachment) >> >> I have searched for this problem and it looks like the issue in embedded >> tomcat plugin. >> (https://github.com/bmuschko/gradle-tomcat-plugin/issues/46) >> > > This is strange - two separate./gradlew runs should be completely > isolated.. the "next time" shouldn't be any different than the "first > time". Are you using Gradle's daemon? Don't- it doesn't work for us, with > the gradle-tomcat-plugin... Note that we disable it via > https://github.com/apache/fineract/blob/develop/gradle.properties - how > are you getting around that?? ;-) > > Could you advice me how to fix this issue? >> Should I use `env=dev` for integrationTests? >> > > Nope, not required. > > BTW we'd like to get rid of the gradle-tomcat-plugin all together. I've > partial WIP re that; details available upon request. Would you have any > interest in helping this project with that? > > Thanks, >> Ivan >> >
