Geek Answers Handbook

What is the general solution for setting up Eclipse for team development?

  • Should each team member create their own workspace and import a project stored under source control? Or is there a way to place the workspace under source control too?
  • How to avoid using absolute paths in workspace configuration?
  • Are there other bottlenecks in this task?
+6
eclipse installation
source share
2 answers

One route user is creating Eclipse projects from an assembly file. This has the additional advantage if the development environment does not have a rigid structure (for example, the path to the X library can be relatively different in the Y environment than in the Z environment), because the same configuration data (files, environment variables, etc.) ) Can be used to set up an Eclipse project as a non-Eclipse environment.

+2
source share

I would not put Workspaces in SCM; which would require that each development environment be identical. Instead, be careful to avoid any hard-coded paths; use workspace variables.

Use Install Project Files to identify and share the sets of projects that you want to import into the workspace. These files can / should be stored in SCM, possibly in specialized release projects.

My practice with serious work on the application is to start with a clean workspace, without extraneous projects. Fill it with the PSF.

+3
source share

More articles:


All Articles