RE: .classpath and .project?

This is a choice thing. Personally, we include all of these files for each
project in the repository so everyone who wants to work on a project gets
all the required setup information as soon as they check out the project.

We also commit our .launch files.

We use classpath variables (Window -> Prefs -> Java -> Build Path ->
Classpath Variables) and string substitution (Window -> Prefs -> Debug ->
String Sub) so no paths are hardcoded within the .classpath and launch
files.

This all works really well for us. Hope it helps.

Greg.

-----Original Message-----
From: Bjørn T Johansen [mailto:btj@havleik.no]
Sent: Thursday, 12 May 2005 8:55 AM
To: users@subclipse.tigris.org
Subject: .classpath and .project?

I have just started using Eclipse with Subversion and I see that these two
files are not
included when I put my Eclipse project into svn. And there is more .xxx
files and I was
just wondering; shouldn't these be added to svn also? Or is this files I
don't really need?

Regards,

BTJ

-- 
----------------------------------------------------------------------------
-------------------
Bjørn T Johansen
btj@havleik.no
----------------------------------------------------------------------------
-------------------
Someone wrote:
"I understand that if you play a Windows CD backwards you hear strange
Satanic messages"
To which someone replied:
"It's even worse than that; play it forwards and it installs Windows"
----------------------------------------------------------------------------
-------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org