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

On Thu, Jun 26, 2008 at 12:39 PM, CARASSO Felipe
<Felipe.CARASSO_at_gemalto.com> wrote:
> Hi Mark,
>
> I was trying to figure out what was happening with Katherine and I
> finally realised that I was missing a little yet very important detail on her
> case. Her svn:external entry points to a local "directory tree", not a single
> folder. Example:
>
> Folder1/Folder2/Folder3 https://someaddy/somerep/someremotefolder
>
> ...where the above svn:external entry is set, say, on "Folder0"
>
> So the API actually creates the local tree and downloads the external
> folder onto "Folder3", but "Folder1/Folder2" remains unversioned, which seems
> logical since they were just created.

Yes, this is something I am aware of from when we first had to add
some support for it. BTW, I am not ignoring this issue, I am just
travelling and will be for another day.

> I suspect that Subclipse (or the lower library) may be barfing when it
> finds such an svn:external entry mixed with unversioned folders in between.

Maybe, but this is something that worked before. Although, it always
showed the folders as unversioned.

>
> Do you think this is a case that was well thought over by the Subversion
> guys? At least we never considered using svn:externals like this in my team.

The Subversion team is not at all fond of the entire feature, so it is
hard to say. The feature is certainly intentional though, as it even
exists in the documentation.

-- 
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