RE: [Subclipse-users] Externals property bug - folder UI

Mark -

Thanks for the response. I still feel like it's a kind of bug, in either
the Subversion API itself or how the Subclipse plug-in reacts to the
.svn folders (or lack thereof in this scenario). I was just referencing
Tortoise if it helped reproduce the behavior.

I'm just frustrated with this behavior because there doesn't seem to by
any way around it, short of simply avoiding the scenario. If you live
with the false positives, you have to be careful to avoid them at every
commit. If you synchronize, override & update the "changes", Eclipse
will actually delete the local copy of your externals - completely
defeating the purpose. I understand why this happens, I'm just saying
it's no longer intuitive.

Katherine Hale
Web Applications Developer, Sogeti USA

-----Original Message-----
From: Mark Phippard [mailto:markphip_at_gmail.com]
Sent: Wednesday, June 25, 2008 10:45 AM
To: users_at_subclipse.tigris.org
Subject: Re: [Subclipse-users] Externals property bug - folder UI

On Wed, Jun 25, 2008 at 6:12 AM, Hale,Katherine <halek_at_oclc.org> wrote:
> OS: Windows XP SP2
> Eclipse: 3.3.2 Europa Winter build
> SVN Team Provider Core: 1.2.4
> Subclipse: 1.2.4 (I think that's the same thing - different panel)
>
> Background:
> We have a collection of projects. Rather than checking dependencies
> into the repository multiple times, we have one project of just
> distributions, and all the other SVN projects reference the jars using
the externals property.
> So a normal project looks like this:
>
> MyProject
> - externals
>
> Nothing else is checked into the externals folder - it just has the
> svn:externals property set to it.
>
> Issue:
> Sometimes the directories that are part of the external don't work
> correctly. When the referencing project's folder is too deep,
> Subclipse does behave as expected.
>
> Base scenario that works:
> <folder>/<folder> <URL>
> But this one would not:
> <folder>/<folder>/<folder> <URL>
> This also does not work:
> <folder>/<folder>/<folder>/<folder> <URL>
>
> It seems very reproducible. When I do a checkout for the first time,
> all of the folders & files come down in the right place. But the
> "middle" folder(s) appear unversioned in the UI. However, when I view
> the same folders in TortoiseSVN, this behavior does not occur.

I have no idea what TortoiseSVN is doing, but those intermediate folders
are unversioned. They do not contain any .svn folder, you cannot add
content within them, and commands like svn info and svn status will
report that the folders are unversioned. We rely on the result of these
API's to know the status.

--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org