The status for this bug is resolved and says the fix applies to 1.0-milestone-2, however I'm running into this same issue still on 1.0-milestone-3.

Here's what I've got (relevant bits only):

rootProject
|- projectA
\- projectB

  eclipseProject { 
      projectName = 'foo' 
  }

  eclipseProject { 
      projectName = 'bar' 
  }

  dependencies {
    compile project(':projectA');
  }

When generating the eclipse project for projectB, it is correctly name 'bar' but references a missing projectA, which is not correct because the project name was set to 'foo'.

The Eclipse plugin is now configured like this (although the old way is apparently still supported):

eclipse {
  project {
    name = "foo"
  }
}

Does this solve your problem?

Thanks Peter, that did the trick!

>When generating the eclipse project for projectB, it is correctly name 'bar' but references a missing projectA, which is not correct because the project name was set to 'foo'.

I think the problem manifested itself because you have generated the eclipse file for a single, specific subproject, right? For example: you change the eclipse project name of project A. Now you need to also generate the files for all projects that depend on A so that their dependencies are updated.

>Thanks Peter, that did the trick!

Cool I bet you have ran the gradle eclipse from the root and that's the reason it worked. The previous way of configuring eclipse (via eclipseProject) should do as well.