Imports: checked (Eclipse correctly points to the method)
Versions: checked (the required dependencies are there and are shown with gradle dependencies)
No previous error: checked (qualifier is defined)
The error persists: checked
Additionally, Eclipse builds the frameworks where Gradle fails.
There are other 56 errors like this one, methods missing from the classes in the jar. Using javap I am able to see that the classes and the methods are there, but the compiler doesn’t find them.
This is my first attempt with Gradle with real world development after reading two books. I intend to migrate all my development to Gradle and Eclipse and in this case I may be following the wrong path, since I am manually (mainly in an effort to deepen my understanding of Gradle) creating the build scripts, without importing the Eclipse project. Another reason why I did not import the Eclipse project is that I will modify the directories layout to adhere to Gradle convention. I will change the project layout after I have it built with Gradle.
When I issue gradle tbenterprise:build --debug I can see that the classpath is properly set up. The Eclipse and Gradle class paths are essentially the same.