[Subclipse-users] Subclipse 1.8.3 issue with working copy of repository subfolder

We just upgraded our environment to SVN 1.7. After upgrading to
Subclipse 1.8.3, I can no longer use working copies that are a subfolder
of a repository. What's strange is it will correctly import a new
project and create the metadata for the working copy, but after the
initial import all the files show as dirty or not part of repository.

I've tried running Team > Refresh/Cleanup and that does nothing.

The only thing I've found I can do is check out the entire repository
and then import the subfolder I need as a new project. This seems to
work fine, but it's not ideal for my situation (it's a huge repository
and I only need to deal with one branch of the repository.)

To clarify the situation, I have a repository that looks like:

Root
        branch
                A
                B
                C
        trunk
                A
                B
                C

Subclipse will allow me to import /Root/branch/B as a new project, but
once it's imported it acts like the project is an invalid working copy.
Everything shows as either dirty or not part of the repository. However,
if I use TortoiseSVN on the working copy, everything works fine. (NOTE:
I only tried testing TortoiseSVN after all my tests with Eclipse, so
this isn't an issue with TSVN invalidating the SVN metadata.)

However, if I check out /Root/ I can then import /Root/branch/B as a new
project and it seems to work ok. The problem is, I don't want to check
out the entire repository (as it's extremely large and mostly irrelevant
to me.)

Is there a way to just check out a specific branch of a repository to a
working copy in Subclipse 1.8.3 or is this a bug?

-Dan

-- 
Dan G. Switzer, II
dswitzer_at_pengoworks.com
http://blog.pengoworks.com/
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2888385
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].