File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes IDEs, Version Control and other tools and the fly likes Project organization with eclipse Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » IDEs, Version Control and other tools
Bookmark "Project organization with eclipse" Watch "Project organization with eclipse" New topic

Project organization with eclipse

Danish Shaukat
Ranch Hand

Joined: Nov 16, 1999
Posts: 340
Hello all,

I wanted some suggestions regarding project organization using eclipse.

I use eclipse for developing J2ME, J2EE, Blackberry and Google Android applications. This means I have 4 different kinds of projects.

Do you think it will be a good idea to have 4 different workspaces for these 4 different types of projects?

saurav sarkar
Ranch Hand

Joined: Jan 07, 2007
Posts: 180

Hi Danish,

I would recommend to have different workspaces, since the idea would be not to clutter the workspace.
Otherwise you can create your own working sets according to your needs.


Be Objectively Oriented.Explore the power of OOPs.
My Blog, Eclipse EMF Query committer.
Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 17410

It isn't necessary. I have all sorts of different projects in my workspace. The main thing is that after a while, the workspace gets littered with projects that don't have to do much with each other. I think in the near future I'm going to create a workspace for the projects of each of my major clients. The main thing to keep in mind is how big you want the workspace to get versus how much of an annoyance it would be to switch to another workspace as you work.

An IDE is no substitute for an Intelligent Developer.
Peter Johnson

Joined: May 14, 2008
Posts: 5852

I have multiple workspaces where each workspace is dedicated to a "project", with the term "project" being used in its loosest sense (not in the Eclipse sense). For example, one of my "projects" is the JBoss in Action project where I maintain the source code for the book. Thus I have a workspace dedicated to it with each chapter of the book being an Eclipse project. No other work is done in that workspace. I also maintain a separate workspace for each "project" at work, usually because each such project requires its own configuration settings.

I also have multiple installations of Eclipse, some of which are dedicated to specific projects. I usually do this if the project has certain requirements, such as plugins, which I prefer to keep isolated. For example, I have a separate Eclipse installation for each book I review, and each has a dedicated workspace.

But it really comes down to your preferences and how you like to work. This system works for me but might not work for someone else.

JBoss In Action
I agree. Here's the link:
subject: Project organization with eclipse
It's not a secret anymore!