Hi all,
I've posted on here before asking why externals defined on a folder a
couple of levels deep appear in subclipse as unversioned. As in this
instance:
/subfolder/myexternal http://myrepository/theexternal
I understand that that is due to the fact that this is what is reported
by svn status and therefore not a problem with subclipse per se. However
I've realised there is a small gotcha with this that may not have been
foreseen, which is that you cannot use subclipse to do a switch on the
external. The only way that I know of to switch this external within
subclipse is to either change the external definition and update, which
is a pain and may not be desirable (I often switch externals to a
different branch for development, but it doesn't mean I want the parent
branch that contains the external to point to the new place
permanently). Or the other alternative is to use command line svn.
It would be nice to be able to do it all within the friendly GUI of
subclipse. I realise the root cause is that svn status reports the files
as unversioned, but it seems that subclipse has come up with other
non-standard workarounds for annoyances within svn before. Take for
example the fact that an svn commit on command line will ignore
unversioned resources, whereas subclipse throws up a dialog that allows
you to select the unversioned files and do the add and commit for you.
So, if svn status doesn't give subclipse the info it needs to figure out
something is an external, why not add an extra check? If svn status
reports a folder as unversioned, run a second svn info on the folder
itself and find out if that's really the case.
Cheers
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Fri Apr 27 09:38:22 2007