Eclipse: Some or all projects can not be imported because they already exist in the workspace

eclipse can't see project in workspace
eclipse import already exist workspace
a liferay workspace project already exists in this eclipse instance
some projects are hidden because they exist in the workspace directory
unable to import project in eclipse
eclipse file already imported
java eclipse folder already imported
sts project already exists

I'm sorry, I know that question is asked quite often. But non of the scenarios suits my problem.

I'm using Eclipse (in Win7) with Git. Within a Git-branch I created a new project. Then I switched back on the master-branch. There the project is not in the workspace. But when I want to add it, I get the following error:

Some or all projects can not be imported because they already exist in the workspace

My problem is, that the project is NOT in the workspace - as seen in Eclipse. But sure, it's on the hard disk, because it's part of my Git repository. So I can't delete it there. According to other posts, I removed it from this folder:

C:\Development\workspace.metadata.plugins\org.eclipse.core.resources.projects

But still I can't re-add it to the Eclipse workspace. Any idea?

Use "file" --> "import" -->"Existing Projects into Workspace" to import the Project that exists on your HDD

Newcomers » reopen a project, I use import -> existing project into workspace -> select root directory and find my project. Then, I somtimes got: Then, I somtimes got: "Some > projects cannot be imported because they already exist in the > workspace", which Copyright © Eclipse Foundation, Inc. All Rights Reserved. Back to the top. Therefore while I understand that doing getAllContentsOfType should find everything, there should be no Statements block which is a common ancestor of Sheep and Pig (I have confirmed this in the Outline view), and the search for all VarDeclarations should not find the declaration of Camel because it is not a VarDeclaration, it is a LocalVariableDeclaration.

This usually happens when you change the project directory physically without first delete in Eclipse. You can view and delete these hidden projects in the following view:

Window -> Show View -> Other -> Navigator

Then simply just continue with the process of import existing project.

353323 – Eclipse Import Projects wizard gives project already exist , View All Add an attachment (proposed patch, testcase, etc.) You will get "Some projects cannot be imported because they already exist in the workspace" error Warning and Finish button disabled. I haven't tried with  This is useful because this avoids being affected by other project's contributions and allows you to get rid of the UML complexity, but it can be painful when you actually want to add a few things on top of UML (I'm not sure if there is a way to reuse/extend an Architecture Framework).

  1. Go to Window-> Perspective -> Open Perspective -> Java EE

  2. Right click on the desired project and remove it

  3. Go to File -> Import -> Existing Projects into Workspace

Eclipse Import Project Some projects cannot be imported because , Eclipse Import Project Some projects cannot be imported because they already exist in the workspace. Last Update:2018-09-08 Source: Internet. Author: User. I've just been encountering a very similar issue in Ubuntu while trying to get Eclipse Mars and Tomcat7 integrated because Eclipse was expecting the tomcat configuration files etc to be all in the same location, and with the necessary permissions to be able to change those files.

Window -> Show View -> Project Explorer

After that, right click on the project name and Delete :)

When eclipse is imported into the project, Some projects cannot be , Some projects cannot be imported because they already exist in the You have just to deselect the active working set and all opened projects will become visible​. When eclipse ask you about workspace make sure that ".metadata" isn't in  You’re right, this is not required by the specification…. but it’s used in the specification, so some users have come to expect it. 4. This can be done from the tree editor by saving as a file with ‘.xmi’ as an extension; mind you, the tree editor is only meant to serve as an example.

Verify that the project is created in the directory and that you are not filtering the projects by the Working Set.

I hope this can help, I didn't realize that I was filtering through the Working Set and that's why I couldn't import the project, because it was already imported but I just didn't see it.

2629758 - Eclipse error: "Some projects cannot be imported , Some projects cannot be imported because they already exist in the workspace, causing the next button to be unavailable. Solution: Check the checkbox in front of  This book contains course notes covering Enterprise Computing with Java. This comprehensive course explores a variety of modern Java frameworks and technologies that can be used for developing mission-critical complex enterprise applications.

Some projects cannot be imported, 2629758 - Eclipse error: "Some projects cannot be imported because they already exist in the workspace". Symptom. When you try to import a project in a target  Commits all imported/processed files in a shared project to the project's underlying repository. The <comment> is optional and is saved with all commits in the headless session. Commits do not apply when the -readOnly parameter has been enabled.

Improve the setup for importing in Eclipse · Issue #3176 · scala-js , Said Eclipse: "Some projects cannot be imported because they already exist in the workspace". Which means: "Some projects cannot be  KT-35442 KotlinMPPGradleModelBuilder shows warnings on import because it can't find a not existing directory; IDE. Gradle. Script. KT-31976 Adding a space in build.gradle.kts leads to 'Gradle projects need to be imported' notification; KT-34441 *.gradle.kts: load all scripts configuration at project import

Some projects cannot be imported because they already exist in the workspace or their project description file is corrupted Invalid project description the solution is to use unique name := "Scala.js XXX" stanza for all projects. Sometimes they even have to get projects from multiple repositories. This is a painstakingly long and error-prone task. But an easier way to manage multiple projects is with Eclipse’s Team Project Sets (TPS). Creating a workspace becomes as easy as importing an XML file and waiting for Eclipse to do its job.

Comments
  • Use file --> import to import the project to eclipse workspace.
  • That's what I did! Import --> from Git --> local repo. It finds the project, but I can't check/select it because it says the error mentioned above.
  • Use "file" --> "import" -->"Existing Projects into Workspace" to import the Project that exists on your HDD
  • Thanks, that worked. Post it as an answer and I will accept it, so that you gain the reputation. Thanks.