I have a question about how the Gradle Eclipse plugin fails to generate Java Build Path “Source” folder entries.
I have been playing around with this plugin but can’t seem to figure out the use of it.
I have a multi-project Gradle build, that is laid out like so:
root/ subprojects/ ---- core/ (utilities) ---- proj1/ ---- proj2/ ---- etc.
But, when I include the ‘eclipse’ plugin and run the ‘eclipse’ build task, the .project file and .classpath file that is generated does not include the proper source configuration to enable intellisense to work.
Am I overlooking something here or is this a limitation of this plugin?
I was expecting the generated files to somehow configure the eclipse project to include ‘src’ folders for my multiple projects by reading the ‘settings.gradle’ file and computing paths to my sub-projects for Eclipse.
If I am misunderstanding this, is there any more information available anywhere besides the limited information in the documentation (http://gradle.org/docs/current/dsl/org.gradle.plugins.ide.eclipse.model.EclipseProject.html) ?
Now, when I examine the .classpath file for one of my sub-projects, I see the following contents are included:
<classpathentry kind="src" path="src/main/java"/> <classpathentry kind="src" path="src/test/java"/> <classpathentry kind="src" path="src/test/resources"/>
BUT, interestingly enough, Eclipse does not read these entries because Eclipse loads only one .classpath file, which is the one in the root of the project rather than the subproject.
Otherwise, it seems it might have worked.
What is the secret to getting intellisense working in a multi-project build?
My project is at https://github.com/djangofan/WebDriverTestingTemplate and I am trying to alter the project to use the ‘eclipse’ plugin and get intellisense working.
I can get intellisense working somewhat, by including compiled .class files in the build path, but that doesn’t give me intellisense BEFORE I have compiled.