[news.eclipse.newcomer] Re: Managing multiple branches with linked resou

[bruce.edge@xxxxxxxxx (Bruce Edge)]

Eric Rizzo wrote:

> Bruce Edge wrote:
> > Eric Rizzo wrote:
> >
> > > Hopefully Dave's response will help you out, but I'm curious about 
> > > something: it's not clear to me why you don't just use multiple 
> > > workspaces, one for each branch. I've been doing that for years 
> > > (mostly using CVS) and it works very well.
> > > Is there something about your needs (perhaps your SCM tool, if it's 
> > > not CVS) that prohibits you from taking that simple approach?
> >
> > > Eric
> >
> > I wanted to use multiple workspaces and redefine the base directory 
> > variables in each workspace and import the projects (not copying) into 
> > each new workspace. This should give me an identical project except for 
> > the base dir in the filesystem where it resides.
> >
> > The main reason I don't keep everything completely separate is that the 
> > project configurations are pretty complex and I don't want to redo all 
> > the setup for each project, and I'd like to keep them in sync.

> I'm not 100% sure what you mean by "setup for each project" but if 
> you're talking about the various Eclipse-specific settings, it can all 
> be stored locally with the contents of the project; in fact, it is 
> usually recommended to check into source control all such things, 
> specifically the .project and .classpath files and the .settings 
> directory (if you have one). On my team we even check in the launch 
> configurations so that everyone launches our app with the same settings 
> during development and debugging.

> Hope this helps,
> Eric

OK, I think I'm getting it here. I had previously let eclipse store 
everything in ~/workspace and then setup links to the source tree.
What you're saying is that I should create the projects in the actual 
source directories (not in ~/workspace) and maintain them as controlled 
source. That would be great if the linked ref dir worked based on the 
source trees root dir.
I found what I was doing wrong there too. I had some dirs that for 
whatever reason were saved in the .project files as absolute path names 
instead of relative to the linked vars. I fixed those manually and the 
link refs work now.

So, regarding what gets saved with the project and checked in, I know 
about the .project file, what about things like .pydevproject, 
externalToolBuilders and everything else I find in the projects dir? Does 
it all go into source control providing I can use the linked dir refs for 
it all?

What files contain the launch configs? 

Thanks again for your help, this is clarifying some conceptual use cases 
that have been causing problems for a while.

-Bruce