.gradle files don’t have an effect because without them your project is still a valid Gradle build. In fact, even an empty directory is a valid Gradle build (try running
gradle in an empty folder in the command line).
I would like to clarify the glossary because I’m not sure what exactly you want to achieve. A Gradle build consist of a collection of projects, each of which is imported as an individual Eclipse workspace project (the project creation wizard is only a specialized project importer). Also, the same projects are presented in the task view.
Since Buildship doesn’t support partial imports, this means that you’ll see all the projects from the Gradle build in your workspace and in the tasks view. If you delete a project and then start a synchronization (right-click on another project and select
Gradle > Refresh Gradle Project), the deleted project will re-appear in the workspace. The tasks view behaves similarly, except there you can’t even delete a project.
This means you can only remove a project from the tasks view by removing it completely from the build like I suggested above. Or, if you want to remove the entire build, you can either:
- delete all projects from the workspace that belong to the same Gradle build, or
- delete the
org.eclipse.buildship.core.gradleprojectnature nature from all
.project files that belong to the same Gradle build.