... *OR* perhaps there is a setting in eclipse to help with the load
project that I don't know about ???
I apologize that that vertically, this will look like a long email, but I
think if I lay it out it s/b obvious ... Here's the situation -
A) we have directories like these in a multi-project build...
myProject
- api
- webService1
- webService2
- integration
- persistance
- common
- account
- order
- services
- service1
- service2
Basically, all the level 2 directories are the real projects while the level
1 directories are just organizational.
B) in the root myProject we have the root build.gradle which starts with:
allprojects {
apply plugin: 'eclipse'
apply plugin: 'idea'
}
subprojects {
apply plugin: 'java'
apply plugin: 'groovy'
... blah, blah, blah...
When we do gradle eclipse, it creates the following:
myProject: .project
api: .project .classpath
all subdirs: .project .classpath
etc ...
But if we try to load existing project into eclipse and browse to the
myProject directory it only sees myProject ".project" file, nothing below.
If I delete myProject/.project, then try the load, it now sees 3 projects to
load: api, integration, and services projects - still not what we want.
Now, if I delete the .project and .classpath files from those three
organizational directories and try again - NOW! Eclipse sees all of the
true projects that need loading.
SO- I either need to exclude the root directory and the 3 organizational
directories from either plugin: eclipse or plugin: java (or both) *OR* find
some setting in eclipse that tells it to continue looking beyond the first
layer.
SO - the question is: What is the proper best-practice method of fixing
this mismatch in gradle and eclipse ??
THANKS!
