Hi Mark,
I think I see what's happening. svn status on the command line does
report the external as unversioned, and I suppose that is where
subclipse is getting it's list of files to update/revert/commit etc.
I guess the difference is that subclipse uses svn status and asks you to
confirm each file, whereas if I do svn revert . -R on the root on the
command line, it sees the externals as unversioned and just ignores
them, but doesn't report anything about them. Which is why they appeared
to work differently and I got confused. Is that right? But yeah, looks
like the problem is in svn itself.
There does seem to be a bit of weirdness in the folder icons, a couple
of f5 refreshes on the Folder1 seemed to flick the icons back and forth
between externals, unversioned, and just the regular version controlled
yellow blob.
Thanks,
Tom
Mark Phippard wrote:
> On 2/15/07, *Tom Walter* <walter.tom@gmail.com
> <mailto:walter.tom@gmail.com>> wrote:
>
> Thanks Mark and Lira. My situation is basically the same as yours
> Lira.
>
> Mark, I'm not sure I explained myself properly, since none of the
> folders are unversioned, they all have .svn directories, and the
> svn:externals property on the root is reported correctly by
> subclipse.
>
> For simplicity's sake, imagine my project looks like this:
>
> MyProject [trunk/MyProject]
> /Folder1 [trunk/MyProject/Folder1]
> /Folder1a [trunk/thirdparty/Folder1a]
>
> Rather than setting the external on Folder1, it is set on
> MyProject like so:
>
> Folder1/Folder1a http://svn/trunk/thirdparty/Folder1a
>
> The command line client handles this OK, it recognises that
> Folder1a is an external whether I run commits/updates/reverts etc
> from the context of Folder1 or MyProject. Whereas subclipse shows
> the unversioned icon on Folder1a and if I try to run any
> commits/updates/reverts etc on either MyProject or Folder1, it
> treats Folder1a as if it was unversioned. I realise I can get
> around this by putting the property directly on Folder1, but
> unfortunately this isn't an option for me.
>
> So it seems that Subclipse doesn't yet handle this case, no
> worries. Since the command line client seems to handle this
> situation, it would be great for subclipse to be able to handle
> this in a future version.
>
>
> Nope, the problem is in Subversion. Try running svn info on one of
> the items that says it is unversioned, that is what Subversion is
> reporting to us. Also, like the command line all of our options work
> just fine. The only issue is the status decorations. See this thread
> in the archives for more details:
>
> http://svn.haxx.se/subusers/archive-2007-01/0058.shtml
>
>
> --
> Thanks
>
> Mark Phippard
> http://markphip.blogspot.com/
Received on Fri Feb 16 02:16:51 2007