[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Using TortoiseSVN with Eclipse workspace breaks it

From: Andy Levy <andy.levy_at_gmail.com>
Date: Wed, 12 Aug 2009 08:41:12 -0400

On Wed, Aug 12, 2009 at 08:22, Schneider, Bjoern /tesa scribos GmbH
HDB<Bjoern.Schneider_at_tesa.com> wrote:
> Hi,
>> Subversion doesn't touch any metadata except the .svn directory. You
>> may need to get back to Netburner on this one to see what they
>> recommend. Or ask on the eclipse users list.
> With 'metadata' I  refered to the directory with the same name in which Eclipse stores it workspace settings, etc.
> I think I boiled the problem down: Eclipse arbitrary deletes and creates files in this directory. So--in Subversion's view--some files went missing and others popped up (without being under svn's control). As these files are needed by Eclipse, you must add these everytime you commit, otherwise a checkout of it simply breaks.

If they are needed only by Eclipse, then svn:ignore them. I have the
following svn:ignore in one of my project roots:


> This idiocy prevents any simple approach to that problem--and you must rely on tools/plugin like Subclipse, which take care to mark obsolete files deleted and add the new ones. I'd really like to know what the Eclipse developers see as advantage of this approach... :-/

The Eclipse developers do what they find appropriate to manage
projects in their application's workspace. If other tools are confused
by this, fix those tools (or don't use them). Add to this the fact
that you're not really using Eclipse, you're using a modified version
of it.

As a general rule, you shouldn't be committing generated artifacts to
the repository, nor workspace-specific files (see above). These should
have predictable names, and as such you can svn:ignore them after svn
deleting from the repository, and then you won't have to worry about

> Anyway, as this is definitely not a TSVN problem (rather a Subversion-Eclipse-interaction one), I'd think we'd schould close this thread :) If someone knows of a magic Subversion property which is assignable to a directory and says something like "always commit this and it contents as-is": I'd be happy to hear of it ;)

I don't think it's a Subversion issue at all here, nor Eclipse (since
you're not really using Eclipse). There is a way to avoid a lot of
this, as I outlined above.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-08-12 14:41:38 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.