Stumped by "workspace already contains a project" error

OK, some additional info:

  • The top-level build.gradle lives in a directory named .../newton.
  • The top-level Gradle project’s name property is not explicitly set, so I assume that property is being defaulted to newton (i.e., the last segment of the containing directory’s path name) and that Buildship is using this property to determine name of the Eclipse project that corresponds to the top-level Gradle project.
  • The pre-existing (added-to-source-control) .project file I mentioned earlier in this thread is not in the top-level directory. This .project file contains <name>newton</name>.

In short, it seems like a setup designed expressly to confuse Buildship :slight_smile: But probably Buildship should handle the situation more gracefully.