Open Graou74 opened 4 years ago
this happens to me from time to time with Eclipse and with JDK8 and i think it's because you can end up with a gradle daemon that is launched from a prior run in Eclipse that never terminates and then the Buildship environment does not sync properly with the filesystem. to get around it,
gradlew --stop
cleanEclipse
task. if this task takes forever, or does not complete it means you did not exorcise the daemons in steps 1 and 2I was able to reproduce this issue.
If a Java package containing the target tests doesn't follow the Java naming convention and starts with an upper case letter then the test execution fails. I managed to write a Tooling API test that reproduces this behavior, which means it's a bug in Gradle.
Hello,
When I run a Gradle test I get the following error:
To reproduce, I create a project with the Buildship Wizard (File> New> Other >> Gradle-> Gradle Project) and from the LibraryTest class of the new project I run the test (right click> Run As> 1 Gradle Test).
The JVM used is OpenJDK-11. I get the same error on Mac Osx (Eclipse "Version: 2019-09 (4.13)", Buildship version "3.1.2.v20190903-1802" or Eclipse "Version: 2019-06 (4.12.0)", Buildship version "3.1.2.v20190903-1732") and under windows (Eclipse "Version: 2019-09 R (4.13.0)", Buildship version "3.1.2.v20190903-1802".
When I run this test with the command line, it runs normally.