| Project setup [message #97085] |
Wed, 24 August 2005 17:30  |
Eclipse User |
|
|
|
Originally posted by: fireonyoursleeve.hotmail.com
I'm setting up a new project using eclipse/cdt/etc. I'm a little bit
overwhelmed with the amount of documentation out there for eclipse and was
wondering if someone could point me toward some best practices for setting
up projects/workspaces for a team environment.
In the DevStudio world, you generally have a workspace file that then
contains multiple projects (maybe each project builds one dll and one of the
projects builds an exe that uses those dlls). All the projects, as well as
the workspace, get checked into source control. What's the analog in the
eclipse world? Do you check in the .metadata directory? If you don't do
you force all programmers to set their directory to the same place relative
to the project? Or is it best to avoid all ${workspace_loc} vars in project
settings then?
At one point I was considering setting up a clean install of eclipse with
just the plugins that would be required to work on the project, then check
that into source control. That way if we upgrade components later we can be
sure that we're all working with the same tools. If code changes need to be
made in sync with one of those upgrades, then they can both be checked in
atomically - i.e. same changelist. The ultimate goal being the ability to
have a new developer come on the team, grab the latest from source control
and immediately be able to build without having to install anything except a
source control client to grab the stuff in the first place.
On the other hand, if that developer is working on another project that uses
eclipse, they already have it installed, probably have a bunch of plugins
they like that might be useful to our project but that we aren't requiring,
have customized all their settings and are happy with them and really don't
want to be force to use our clean setup.
Is there some road between? Where's a good place to find some high level
documentation that might give me a better idea how eclipse treats workspaces
vs client configurations and the designers' vision of how things should be
setup to share across a team?
Thanks!
|
|
|
| Re: Project setup [message #97342 is a reply to message #97085] |
Thu, 25 August 2005 10:38  |
| Eclipse User |
|
|
|
Originally posted by: eclipse3.rizzoweb.com
Aaron Leiby wrote:
> I'm setting up a new project using eclipse/cdt/etc. I'm a little bit
> overwhelmed with the amount of documentation out there for eclipse and was
> wondering if someone could point me toward some best practices for setting
> up projects/workspaces for a team environment.
>
> In the DevStudio world, you generally have a workspace file that then
> contains multiple projects (maybe each project builds one dll and one of the
> projects builds an exe that uses those dlls). All the projects, as well as
> the workspace, get checked into source control. What's the analog in the
> eclipse world? Do you check in the .metadata directory? If you don't do
> you force all programmers to set their directory to the same place relative
> to the project? Or is it best to avoid all ${workspace_loc} vars in project
> settings then?
The Eclipse workspace is not really intended to be a shared resource. It
is generally very machine/user specific, although it is probably
possible, if every user's general file system directory structures are
the same (for things that the workspace and projects might reference
like JDK locations, etc.), to have a "jumpstart" workspace that could be
shared.
What I'm trying to say is that it might be possible to get working, but
you're on your own and somewhat going against the intended design of
Eclipse.
One good reason to require new developers to set up their own Eclipse is
because it encourages newbies to explore around and learn about the
tool. Eclipse is not a minimalist tool and users are best served by
installing and setting up their workspace the way they want it and going
through the tutorials and Getting Started guides. If you just dump a
developer in a pre-configured Eclipse, they will inevitably be less
productive in it than if they spend some time getting familiar with the
tool.
Anyway, if you do decide to go that route, you'll definitely want to
either enforce things like the locations of the workspace, Eclipse,
JDKs, etc. and eliminate/minimize any references to stuff outside the
workspace. Of course specific questions are always welcome on the
newsgroups if something is giving you trouble.
HTH,
Eric
|
|
|
Powered by
FUDForum. Page generated in 0.09392 seconds
Home