Can I use the same workspace for eclipse-java and eclipse-cpp? - eclipse

I downloaded eclipse-jee-juno-SR1-win32-x86_64 and created the workspace folder in mu user directory. Seems to work fine.
Then I downloaded eclipse-cpp-juno-SR2-win32-x86_64, but I cannot find an acceptable folder for the workspace.
How can I keep eclipse for java and for c++ in the same user directory?

Related

STM32CubeIDE deleted all my projects inside workspace

Info:
STM32CubeIDE 1.4.0
OS: Windows
Description:
I have chosen working directory/workspace. E.g., C:\course_1\cubdeide_ws
STM32CubeIDE was closed
I have then renamed my course folder. E.g., C:\course_2\cubdeide_ws
I then opened STM32CubeIDE to do project (STM32-Projects)
I had encountered the following problem:
All projects inside folder/workspace C:\course_2\cubdeide_ws (renamed one) was deleted
I should only have C:\course_2\cubdeide_ws directory in my PC, but I also had C:\course_1\cubdeide_ws
In folder C:\course_2, I had my files from before, but there are no any projects inside C:\course_2\cubdeide_ws folder
In folder C:\course_1 I have a folder with path C:\course_1\cubdeide_ws, but even there, there is none of my projects
Problems:
All my STM32-Projects are gone/deleted (it's not even in Recycle Bin)
Why is STM32CubeIDE creating new folder (same as chosen workspace before)? Before renaming any folder in my PC, do I have to check whether the path is included as workspace by STM32CubeIDE?
I just renamed my folder.Why do STM32CubeIDE deletes projects and also created new folder as per the workspace selected before?

Eclipse workspace corrupted after saving as zip

I have a need to share an eclipse workspace as a zip file. However, when I zip the workspace and then unzip it all of the user configuration is lost including the project that was opened in the workspace, what views are showing, and even a JBoss server that was created.
If I copy and paste the workspace everything works fine.
If I zip and unzip all of the configuration is lost (i.e. when I launch Eclipse and use the unzipped workspace Eclipse opens with all of the default settings including the welcome page).
What could be causing this and how do I get the zip to work?
I know there are other ways to export Eclipse configurations but I do have a specific requirement that this be provided as a zip file.
It looks like the problem was with the file names that started with ".". I re-zipped with WinZip instead of the built-in windows tool and everything is working now. See: blog.robertelder.org/zipping-corrupts-eclipse-workspace

Why do projects that I add to my 'workspace' folder don't show up? [ECLIPSE]

I am using Eclipse Indigo, and after having successfully extracted my project folder into my Eclipse workspace, it does not show up in the package explorer. I tried refreshing eclipse and restarting it, to no avail. I am 100% certain my eclipse is using the right directory and the project is in it.
What could be the problem? Thank you.
EDIT: "import projects into workspace" worked for me, but why was that necessary?
Files in the directory are not automatically picked up by the package explorer. You need to import them.
Try using the File > import, then choose
Existing Projects into workspace.
There is a checkbox that says "Copy projects into workspace" which copies it to your workspace if it happens to be in a different folder. If you start with your files in another folder, you'll see how it's copied and set up with configuration files in your workspace directory.
To answer the question, "why is it necessary to import?" you have to realize that the Eclipse workspace is just a logical container for projects, not necessarily the physical container for them.
Also realize that a directory of project-related files does not make an Eclipse Project; Eclipse must be given or generate it's own set of configuration in order to understand a project (minimally, for Java projects, .project and .classpath). Without those, Eclipse has no idea what to do with an arbitrary folder that you call a "project." That's what the Import or Create Project wizards are doing under the covers, generating those config files.

What is the .metadata folder in Eclipse workspace?

My "workspace" folder includes a hidden folder called ".metadata". Is it important to backup this folder regularly?
The .metadata folder is an area where Eclipse plug-ins can save any information they want to save. This will include things like your preference settings, information about the contents of projects and the indices the Java plug-in uses to find classes and methods quickly.
It also includes the .log file where Eclipse logs errors.
Exactly what is stored there depends on the plug-ins you have installed (one of my plug-ins has a database in the .metadata) so it is a good idea to back it up (along with the projects).

Eclipse does not show projects in workspace

I have opened Eclipse workspace that I transfered from another computer but it does not show any projects in package explorer (there should be a lot of them). Still project's folders are in workspace folder.
The new machine where I transfered the workspace runs Windows 7 that has the read-only folders issue (more here). That is all the folders that are created on that OS are read-only and that the read-only atribute cannot be removed in any way.
Eclipse originally refused to open the workspace at all saying that .metadata folder of the workspace is read only. After turning user control to the lowest level it opens the workspace but it acts as if it did not contain any projects. I think this is because Eclipse refuses to work with read-only folders and project folders are also read-only.
Did somebody have same problem? How did you solve it? Any suggestions are wellcome.
It is not enough to move your projects in the workspace path folder, you also need to import them. And because of they are in your path folder, you can't import them again because it will say you still have them in your workspace. Move them to another folder (for example in desktop), be sure your workspace folder is empty, and then try to import them from your temporary folder in desktop.