From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

image.png

Do as suggested and run with `--stacktrace`, maybe also show more output, or optimally a build `--scan`.

<@URQ797WRW> here is output when running with `--stacktrace`

Don't copy a `tools.jar` into a Java 9+ installation

<https://discuss.gradle.org/t/org-gradle-initialization-exception-initializationexception-gradle-could-not-start-your-build/45362>

but in my another project, originally I used Java 8 also `tool.jar` , but now I migrated to Java 11 and must copy this file to new jdk folder

You forgot a "not".
You *must not* copy `tools.jar` anywhere.
If you copy `tools.jar` anywhere, you mess things up!
Indeed Gradle should handle the case more gracefully, but you *must not* copy any `tools.jar` to a Java 9+ installation, never ever ever ever ever ever

`tools.jar` simply does not exist anymore in Java 9+ and if you use something that checks for it and complains, then this thing is simply not compatible and not usable with Java 9+

You cannot use a `tools.jar` that contains tools from older Java versions with the new Java versions.
You might in some cases make some stupidly wrong checks satisfied, but you break other things with it and in majorly subtle ways.

Never do that ever. If something needs it, don't use it unless that is fixed to be compatible with Java 9+