What is eclipse workspace

And there is a Project, which means a project. So I would say a workspace is the directory or directories that store your "source" files, or all your files, because they might be more than just source code. I hope I am right. Ernest Friedman-Hill. In IDEA, you can store your source anywhere you want, and someplace, you have a project file for each project. That project file specifies where the source is.

When you open a project file you get a JFrame. If you have more than one project open, you get more than one JFrame. In Eclipse, you have to store your source in a project directory, which in turn is a subdirectory of a workspace directory. A workspace is nothing more than a collection of projects. You can have more than one workspace, but you have to launch a new copy of Eclipse to use a different workspace.

Now, both of these are simplifications to some degree; with some effort, you can make each IDE act more similar to the other. But that's the fundamental difference: Eclipse wants you to put your sources into a project directory inside a workspace, and IDEA really has no similar concept. Bharat Ruparel. Actually, it might be little bit of overgeneralization. In reality however, and in a shared development environment using a source-code control system such as ClearCase, Eclipse very nicely allows you to store your files externally using linked folders.

The eclipse help system does a good job of explaining this. Isn't that what I said? Eric Clayberg. Actually, your project directories can be anywhere. Ko Ko Naing. That's what I am finding for The exact definition and nature of workspace and project, while I can't find such things in JBuilder Thanks a lot to Dr.

Ernest and Mark for the great explanations Yes they can. They are using Eclipse, because they are waiting for the red-tape to buy the licenses for IDEA Although some might still stay with Eclipse. Specify Parameters Template Configuration template-config. How do I see and configure the key shortcuts? Are there any backup files in Eclipse? Workspace in use, cannot launch eclipse Locking is not possible in the directory How to start DVT Eclipse with a different eclipse.

Can I perform dos2unix or unix2dos from DVT? I am using the Common Desktop Environment via Citrix and experiencing crashes.

What can I do? How do I change the background color of the Editor? Some widget colors are not displayed properly. How do I change the tooltip colors? How do I change Internet Proxy Settings? Eclipse does not start, there is no Workspace, metadata or log file created Workspace permissions How do I link mylyn with Bugzilla? How do I print source code? How do I disable Eclipse Software Sites? How do I revert to a previous version? An RCP application can be a different beast depending on what its used for but in the true IDE sense I don't know what would be a better solution than a workspace or context of projects.

Just my thoughts. First point and primary is the eclipse it self and is related with the settings and metadata configurations plugin ctr. Each time you create a project, eclipse collects all the configurations and stores them on that workspace and if somehow in the same workspace a conflicting project is present you might loose some functionality or even stability of eclipse it self. And second secondary the point of development strategy one can adopt. DLTK for examples is a beast that should be contained in a separate cage.

Lots of complains at forums for it stopped working properly or not at all and suggested solution was to clean the settings of the equivalent plugin from the current workspace. Personally, I found myself lean more to language distinction when it comes to separate workspaces which is relevant to known issues that comes with the current state of the plugins are used.

Preferably I keep them in the minimum numbers as this is leads to less frustration when the projects are become Finally, loading speed and performance is an issue that might come up if lots of unnecessary plugins are loaded due to presents of irrelevant projects. Bottom line; there is no one solution to every one, no master blue print that solves the issue.

It's something that grows with experience, Less is more though! Although I've used Eclipse for years, this "answer" is only conjecture which I'm going to try tonight. If it gets down-voted out of existence, then obviously I'm wrong. Within the Solution are "Projects" that can be compiled individually or collectively by the Solution. Each Project has its own makefile, compiling its portion of the Solution with settings that are different than the other Projects. Similarly, I'm hoping an Eclipse Workspace can hold my related makefile Projects Eclipse , with a master Project whose dependencies compile the various unique-makefile Projects as pre-requesites to building its "Solution".

My folder structure would be as Rafael describes. So I'm hoping a good way to use Workspaces is to emulate Visual Studio's ability to combine dissimilar Projects into a Solution.

Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Eclipse Workspaces: What for and why? Ask Question. Asked 8 years, 11 months ago. Active 7 months ago. Viewed k times. Can anyone give a detailed, but not a page long insight into this? This involves a lot of sub-questions, so to speak, and I don't know all the specific sub-questions I should ask, as I am sure I don't know all aspects of Eclipse and Workspaces , but I'll try to give an example of what I am looking for: What for?

What did the Eclipse development team expect it to be used for? What do you think? Are there configuration conflicts vs. Any filespace reasons? Improve this question. Stu 9, 3 3 gold badges 7 7 silver badges 24 24 bronze badges.

I still don't get it. It apparently just makes sense to people who already know the what for , and is hard for them to understand that this is not obvious for everyone else out there. Why I didn't accept an answer yet. That, I get. Add a comment. Active Oldest Votes. What it is A workspace is a concept of grouping together: a set of somehow related projects some configuration pertaining to all these projects some settings for Eclipse itself This happens by creating a directory and putting inside it you don't have to do it, it's done for you files that manage to tell Eclipse these information.

Exploring each item above: a set of somehow related projects Eclipse seems to always be opened in association with a particular workspace, i. Improve this answer.

Community Bot 1 1 1 silver badge. Rafael Eyng Rafael Eyng 4, 1 1 gold badge 31 31 silver badges 34 34 bronze badges. I admit the last section needs some clarification. What is a sub-project, if not a project itself? How does these sub-projects make up for being used across different workspaces without using the whole parent project?