This is informational, and not reporting a bug - it's more of a
request for documentation.
I've been using TortoiseSVN for about a year, but just started using
it for an Eclipse project. (Of course) Eclipse copies files from the /
src directory to the /bin directory, I just never thought about it.
This manifests itself somewhat strangely. I have the /bin folder
ignored globally in the TortoiseSVN settings. However, TortoiseSVN
sees that the /bin/.svn/ exists, and so it marks the /bin folder as
"modified" instead of "ignored", as well as the parent of /bin (i.e. /
ProjectFoo/). If I "check for modifications", it shows that there are
none, and there is (correctly) nothing to commit.
An interesting sidenote is that it gave me the option to do a "svn
delete" on the files in the /bin folder, even though they were never
added to .svn. The result was that the matching files in /src were
deleted instead, since that's where the metadata in /bin/.svn/ pointed
to (since the metadata had been copied by Eclipse). It's probably not
worth the development effort, but perhaps TortoiseSVN should have a
check for the validity of the information in the .svn/ folders instead
of using them blindly. That is, "Hey, this metadata is located in /
bin/.svn/ but points to /src/, therefore /bin/ is obstructed".
Here's a blog post showing how to exclude the files from an Eclipse
project: http://francisoud.blogspot.com/2008/07/eclipse-classpath-ad-subversion.html
Long story short, I think it would be a great idea to add something
either in the manual, FAQ, or both, which says: "Hey! You! Make sure
your IDE doesn't copy the .svn/ folders to your output directory!
Results are undefined if there's garbage data in .svn/ folders, crazy
crap might happen!".
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-11-26 03:10:53 CET