Bug with subclipse, where it thinks I have code changes when I actually do not.

The best way to describe this is with pictures, but I'll attempt to use words.

In the resource perspective, project explorer view, where it shows a tree of your source files, I use label decorations to show outstanding differences in my working copy.
When I check out my working copy fresh from my svn repository, Subclipse will show certain directories as having an update, but if I go to the command line and use svn status,
there are no outstanding changes. It only seems to affect certain directories and files in my working copy. I have no idea why those particular directories and files are affected.

[cid:0C2D79E0-869E-4721-AA94-0B9144F04C7D]

If I go to the command line at the 'lwisi' directory, and do svn status, there will be no outstanding changes:

$ pwd
/Users/jakehurst/workspace/head/src/ports/distfiles/lwisi
$ svn status
$

Remember, this is on a *fresh* svn checkout.

Has anyone seen this before? How do I fix this? Is this some sort of deep repository bug that when I check out my working copy, it comes over as broken?

Environment:
OS X 10.8.3 (with stock Java from Apple, fully patched)
Eclipse 4.2.2 build M20130204-1200
Subclipse:
subversion client adapter 1.8.3
subversion javahl 1.7.8.1
svn team provider core 1.8.18
CLI Subversion (from MacPorts)
  subversion @1.7.9_1 (active)
  subversion-javahlbindings @1.7.9_0 (active)

Thanks for your time,

-Justin Akehurst
Senior Software Engineer
EMC Isilon Storage Division
justin.akehurst at emc.com

------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=3055277

To unsubscribe from this discussion, e-mail: [[email protected]].