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

Re: Strange behaviour with Eclipse and directories.

From: Andy Levy <andy.levy_at_gmail.com>
Date: Tue, 17 Jun 2008 08:44:36 -0400

On Tue, Jun 17, 2008 at 8:38 AM, Jonathan Belson <jon_at_witchspace.com> wrote:
> Hiya
> I've recently started to use TortoiseSVN 1.4.8 and I'm seeing strange
> behaviour between with it and some Eclipse projects. To briefly describe:

Before I attempt to answer anything, why aren't you using Subclipse?

> I have an Eclipse project 'Sample', consisting of a directory 'Sample',
> source files 'File1.java' and 'File2.java', and Eclipse files '.classpath',
> .project' and 'build.xml'.
> Sample
> File1.java
> File2.java
> .classpath
> .project
> build.xml
> All files are under subversion control. When I do a fresh check out, they
> each have a green tick on their icons, as expected.
> When I load the project into Eclipse, it compiles the java and puts the
> .class files into a new directory called 'bin'. However, 'bin' has a red
> '!' on its icon. I originally thought this was because it is an unmanaged
> directory inside a managed directory, but the .class files themselves don't
> have any kind of TSVN graphic on them. Also, 'Unversioned files mark parent
> folder as modified' is not checked, but the red '!' is propogated upwards
> through the directory tree.
> I also notice that the new 'bin' directory contains an '.svn' directory,
> plus versioned files '.project', '.classpath' and 'build.xml'! Why does the
> new dir contain subversion files; is Eclipse trying to be 'clever' and doing
> this automatically?

Most likely it's auto-building your project and the configuration is
such that *everything* is copied to that build directory - including
the .svn directories.

> I also tried to use the 'svn:ignore' property to make the 'Sample' directory
> ignore the 'bin' directory when it gets created, but it appeared to have no
> effect as the '!' graphic still appears.

Because the Subversion libraries think that it's a different directory
from what it appears.

> Can anyone shed any light on this behaviour? I can work around the problem
> by telling Eclipse to put the compiled .class files directly in 'Source'
> rather than 'Source/bin', but it's not a very satisfactory solution.

Again, why aren't you using Subclipse in the first place?

To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-06-17 14:44:45 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.