up to you! i've always found keeping the related versions of different projects, which belong to the same release in a given workspace a cleaner approach. that way, i could switch between workspaces whenever i need to refer to something in a separate release, and switch back to the current release workspace. it also saves me from the hassle of checking-out, or browsing the repository.
you may also want to keep in mind that you can open multiple instances of eclipse as long as they are looking at different workspaces. not sure if that is important to you, but i like doing that from time to time.
i like to use several decoupled workspaces (which differ depending on the type of project), which import projects from various locations. easy to move things around, without creating a ton of similar workspaces. plays nice with my scm too.
depends on how many projects do you work?if you work on many projects, i'd use same workspace, because if you use several you can easily forget what is where and that can be frustrating to say at least. however i always use different workspace for different programming languages that way its less confusing, when you're in java workspace you think java :d
i have all my projects in single workspace and use working sets to manage them.
i would use separate workspaces for different "groups" of projects. for example you might want to combine your main app project and the unit testing project together in the same workspace.
maybe i'm unlucky, but eclipse often (once a month, say) dies on startup, typically in the "initializing java tooling" stage. the recommended solution seems to be to create a new workspace. if you have all your projects in one workspace, this can be a pain. i think smaller workspaces may mean the crash is less likely to occur.
as the preferences are workspace-specific, i tend to have a enormous workspace open - i'm too lazy to sync some settings between workspaces (e.g. repositories...).
on the other having too much projects open in a single workspace can slow down eclipse - so the least i have to do is to close projects i'm not working with. i manage a lot of relative short-term projects (at most one month) in eclipse, that reside in the same workspace (and in most cases the same repository), so this setup gives me a bigger flexibility.
if you have several, interrelated projects, then keep them in the same workspace. if you can identify group of projects, that are always used together, but the groups are used independently, then put such project sets into different workspaces. in that case that should be the logical structure.
we have a situation where we have several projects, some on branches, which frankly is too impractical to keep in the same workspace - and working sets are a joke. unfortunately. also having projects open you do not use, may accidentially be chosen from completion menues, etc. error prone.
the really nifty feature for us, was when team -> project sets were added (in eclipse 3.3 i believe) as this allowed us to have a single file describing the many projects making up the whole application, which can be imported in eclipse with team->import. need a given project? check it out of cvs, locate the projectset.psf file inside of it, and import that.
this has proven to work well for us.
i have one workspace per type of project. ex: plain java, web application, python etc.
the reason being i can share libraries that are similar without copying or pointing to them. also, i close the unrelated projects from eclipse to avoid clutter.
if the projects are interrelated (i.e. have dependencies on each other) then it quite often makes sense to have them in the same workspace. also, if you are working on several projects to solve a related problem, the same applies.
you will waste a lot of time changing workspaces unnecessarily otherwise, especially when the ide will immediately show you the impact the changes in one project has on another.
not only do i keep separate workspaces for each project but i keep separate copies of eclipse also. this is because i typically have to put projects on ice for long periods and return to them (with little notice) and they absolutely must build. i can't take the chance that some plugin i've installed for my latest project (maven based) will interfere with the build process of one of the legacy systems (ant based). for the record i do document the eclipse environment for those legacy systems but i don't have time to mess with eclipse when patching a production bug.
i create eclipse workspaces around products, because for me, a product can have multiple projects within them, for example like having core libraries compiled into one jar in a project, this is used by other projects.
in terms of production environment, you would want products running in different directory structures, much cleaner that way. and in eclipse the workspace creates a directory with workspace name. so, create workspaces based on product/app rather than one or more projects within them.
i used to keep separate workspaces, but got tired of the difficulty in keeping settings consistent between them. now what i do is create working sets for different projects and change the current window working set to filter out everything except what i want to work on. so far this has worked fine for me.
since each project can have multiple working sets, and the window working set can be any combination of working sets, it's quite easy to only see what you want at any given time this way.
- should I create workspace for each java project in eclipse
- Eclipse: Should I create a workspace for each project?
- How to create a jar file for the eclipse plugin project that should be able to download and run without eclipse software?
- Multiple Git repositories for each Eclipse project or one Git repository
- How to create the pom.xml for a Java project with Eclipse
- Eclipse Plugin and ADT modification for API Integration in Create Project menu
- Create a project in Eclipse in a subfolder of the workspace
- What files should be committed to github for an eclipse project
- Create jar for android project in eclipse
- Can't create Run/Debug configuration for AspectJ project in Eclipse
- How create a java project for both intellij and eclipse ide's
- How to create laravel project using eclipse for PHP Developer
- A lot of error when create new project in eclipse for Android App
- Cocos2d-x-2.2 for Android - create new project on Eclipse
- How to create project setting for Eclipse IDE of a Play Java project
- Create WAR file from command line for Eclipse Dynamic Web Project
- How to setup the project & workspace for building Androlate; an Eclipse Plugin
- How do I create a new eclipse project for jetty from a tomcat based project and versioned with svn/subclipse?
- Create a new Eclipse Project for Xampp
- Assigning a perspective for each project on Eclipse
- How to create a basic camel project with mvn for eclipse (for dummies)?
- Create our own property page for project explorer eclipse plugin
- When I create Eclipse projects, are the Java/Android dependencies copied again for each project?
- Creating ant build.xml files for each project in workspace
- Not able to create runnable jar for eclipse project
- Why should we use multiple Eclipse "Java Project" for multiple layer architecture within single workspace
- Soyatec eUML2 free edition cannot create a project for it in Eclipse
- Eclipse : Create a workspace around an existing project
- gitignore in Eclipse workspace rather than each project
- How create a simple maven project in eclipse for develop portlet liferay 6.2 with primefaces (on jboss)
More Query from same tag
- Eclipse's 'syso' Shortcut is Not Working?
- Eclipse cannot find dependencies of a plugin built with Maven Tycho
- Automatic indentation on Eclipse PDT when copy-pasting
- C++ Run time Linker error (liblog4cpp.so.5) Eclipse
- Joining Two Entities in Spring Data JPA
- Android App Error: java.lang.NoClassDefFoundError
- How do I use account registration in my app?
- Move a ball in bowling game once a key is pressed
- Removing EMF dependencies
- cannot run service jboss eap 6.4
- Is there any way to import a .CAR file (WSO2) to Eclipse Developer Studio?
- ClassPathHelper plugin not recognized by Luna
- java.lang.RuntimeException: Application "org.eclipse.ui.ide.workbench" could not be found in the registry
- Eclipse Not recognizing Environment Variable (Mac OS Lion, Eclipse Juno 64-BIT)
- How does the Java VM decides the value of the user.dir System property?
- How do I add an AsyncTask to this?
- Eclipse debugger always blocks on ThreadPoolExecutor without any obvious exception, why?
- How to debug lambda expression in Java 8 using Eclipse?
- Use Eclipse Runtime Configuration to start jar file
- Upload file from webapp with selenium webDriver
- how to setup eclim with android developer tool (eclipse 4.2)
- Eclipse IDE started and broken - cannot find any Java classes
- Eclipse pydev 'F3' doesn't jump to definition
- How to manage build.<username>.properties file content with Liferay IDE?
- Android Threaded Canvas problems with Sensors
- Including Google Play Downloader Library | APK File Expansion Library
- ubuntu openjdk-7 the link "src.zip” is broken
- Jar Export Shortcut Key in Eclipse?
- Where to place gradle build file?
- tip calculator error android 2.2 app