Re: [Subclipse-users] subclipse 1.2.0 along-side Tortoise 1.4.3

On 2/28/07, RChaddock <robin.chaddock@iplay.com> wrote:
>
> Mark Phippard-3 wrote:
> >
> > On 2/27/07, Robin Chaddock <robin.chaddock@iplay.com> wrote:
> >>
> >> I know its a common question, but I am having unexpected problems
> after
> >> recently upgrading both of them to the latest versions.
> >>
> >> By my understanding both subclipse 1.2.0, and tortoise 1.4.3 clients
> use
> >> the same subversion file format (1.4.3), yet subclipse has all sorts of
> >> problems in the synchronize view.
> >> Are they not as compatible as they should be? or is it simply subclipse
> >> is
> >> abit broken?
> >>
> >
> > You do not say what the problem is. There is a known problem of the
> view
> > not always refreshing after certain actions, an issue has been filed for
> > that. I do not think any of this would have anything to do with
> > compatibility with TSVN though.
> >
>
> There are several problems i'm seeing in the synchronize view :-
>
> 1) 'synchronize' is not displaying all the items it should be (files that
> have changed, are being ommitted from the view)

That is the issue I mentioned previously. I believe that toggling the view
between Incoming and Outgoing modes will cause the files to be displayed.

2) rogue root directories are being displayed, both inside and/or along-side
> itself e.g.

This is a feature, see:
http://markphip.blogspot.com/2006/12/subclipse-synchronize-feature-show-out.html

>>
> >> Does anyone else wish that subclipse recognised linked folders as being
> >> svn managed?
> >> Definitely my number one RFE.
> >>
> >
> > That feature is not likely to ever happen. When you use linked folders,
> > you
> > are using an Eclipse-created notion of the file system layout and there
> is
> > no way for the Subversion API's we use to be aware of this.
> >
>
> That is a real disappointment, for the project structure we work with -
> linked folders are essential.
> My field is J2ME development, primarily focussed on porting.
> We operate with a shared code-base that will typically be ported to work
> on
> 300+ different handsets.
> Different portions of the code base are compiled against different device
> libraries, therefor we have an eclipse project per device, configure the
> classpath to contain the libraries for that handset - and then gain access
> to the shared source tree via a linked folder. (we then place onto the
> classpath the source & resources for the given device)
> Presently to work around the lack of link support, we create an additional
> plain/general project that simply encompasses the shared source tree,
> giving
> us a way to use subclipse. (however this isn't ideal when wanting to do
> svn
> operations - in particular compares.)

The usefulness of the linked folders feature is not in question, so your
particular reasons for using it are not that relevant. The feature is not
supported because doing so with Subversion, which has its own rules about
the file layout would be difficult or impossible. Since you did bother to
include the reasons you are using the feature, I can tell you that you could
get the same behavior using the svn:externals feature. Since this is a
feature of Subversion, rather than Eclipse, it is supported and would work.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/