Here is a project that reproduces the first problem (error in console if you don't add the JUnit library to the project, although JUnit4 is in the project B classpath thanks to the Gradle Dependencies).
- unzip the attached project
- import with the Gradle import wizard
- go to testb.TestB in project B
- right click in the editor, Run As => JUnit Test
You'll see the first exception in the console.
Unfortunately I was not able to reproduce the second problem: if I add the JUnit library to B, the test case works, although I would expect it to fail since it uses a classes from Glazed Lists JAR which is contributed by the Gradle Dependencies library...
However I observed that once I removed project C (from settings.gradle of the root project and from the dependencies of build.gradle of project B) and the src/main/java folder of project A (which is useless for this demonstration), then the Run As => JUnit Test started to work perfectly, even without the need to add the JUnit library to project B...
So, maybe also the second problem, which I'm not able to reproduce with this simple test case, is in some way bound to the fact that the project where I see it have a complex dependency graph between projects and something is triggering this strange behaviour...