You might be running into this: https://stackoverflow.com/a/52510288
On Mon, Oct 1, 2018 at 2:03 PM Patrick Rhomberg <prhomb...@pivotal.io> wrote: > Hello all. > > I've been getting some strange failures lately, with the output given > below. I have noticed that creating a `gradle wrapper` fixes these > issues. However, since the gradle wrapper is part of the git tree, I was > curious to know if anyone else was having this problem. > If so, we must've committed a bad jar somehow. If not, I'll continue to > try to suss out how I've dirtied my local environment. > > Imagination is Change. > ~Patrick > > Gradle output: > > |develop → origin ✓| → ./gradlew dev > Starting a Gradle Daemon (subsequent builds will be faster) > > FAILURE: Build failed with an exception. > > * What went wrong: > Unable to start the daemon process. > This problem might be caused by incorrect configuration of the daemon. > For example, an unrecognized jvm option is used. > Please refer to the user guide chapter on the daemon at > https://docs.gradle.org/4.10.1/userguide/gradle_daemon.html > Please read the following process output to find out more: > ----------------------- > > FAILURE: Build failed with an exception. > > * What went wrong: > Could not create service of type ClassLoaderRegistry using > GlobalScopeServices.createClassLoaderRegistry(). > > * Try: > Run with --stacktrace option to get the stack trace. Run with --info or > --debug option to get more log output. Run with --scan to get full > insights. > > * Get more help at https://help.gradle.org > > > * Try: > Run with --stacktrace option to get the stack trace. Run with --info or > --debug option to get more log output. Run with --scan to get full > insights. > > * Get more help at https://help.gradle.org >
