How to organize “projects” and “solutions” in Eclipse?

I don't think, the Eclipse workspace is equivalent to the VS solution. An Eclipse workspace stores a lot of meta-information about projects, their physical location (possibly in or outside of the workspace folder), etc. , and even workbench settings.It is not a good idea to upload this information into source control, as it is possible that other developer uses other physical locations for the projects, etc.

I don't think, the Eclipse workspace is equivalent to the VS solution. An Eclipse workspace stores a lot of meta-information about projects, their physical location (possibly in or outside of the workspace folder), etc. , and even workbench settings.It is not a good idea to upload this information into source control, as it is possible that other developer uses other physical locations for the projects, etc. There is a similar concept in Eclipse to the solutions (similar, not equivalent): Project sets. It is only a GUI option to group your projects into sets.

These sets cannot be executed together, and is only visible in the Project navigator. Another way is to create multiple workspace folders, and you can use them as an alternative to solutions. The drawback of this approach is, that if you customize the IDE (e.g.By using Preferences, or by defining source control locations), these customizations have to be made in every workspace.

This issue can be handled using the Workspace Mechanic tool (I haven't tried it, but it can migrate these settings).

The main reason why it is better FOR ME to have a separate workspace for a single project is performance and lucidity. With many projects within one workspace, you'd have to close the other ones because of shared classpaths for editor assistance. Editor uses classpaths of all projects for content assist, class hierarchy lookup etc.Eclipse anticipates that the open projects are related.

And when using project managers like Maven, one maven project is usually divided into many little eclipse projects. It's simply a best practice to have a separate workspace for a project. Second reason is, that usually you'd need to import another related project to see how things are done and it would be terrible mess then having it all in one workspace.

You definitely shouldn't commit the . Metadata folder into source control. You commit only the projects inside.

Because you and others then will check out the project only into their own workspace. But it is a question whether you should commit the . Project file, because it's personalized and eclipse version specific and things like project nature (java, spring, maven nature etc. ) can anybody set up by himself.

. Classpath files in the project should be committed to the source control, because they specify classpaths, it would be very time consuming setting it up again.

A workspace is simply a set of buildable projects that someone is working with. Using a separate workspace per project can be harmful, as is a blanket declaration that it is a best practice for all cases. – Andy Thomas-Cramer Sep 29 '10 at 18:02 If you downvoted me, at least reveal the secret why having a separate workspace per project can be harmful.

I'm using eclipse 4 years every day, I know what I'm talking about. The only truthful fact is, that not having separate workspace per bigger project can be harmful...if you know how to easily sync settings. – Sloin Sep 30 '10 at 12:08.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.