[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: architecture questions

From: McClain Looney <m_at_loonsoft.com>
Date: 2003-12-11 02:07:03 CET

On Dec 10, 2003, at 6:31 PM, Geoff Howard wrote:
> Unless something is mislabeled there, there is no M5 build for
> windows. Just two linux builds and a panther build.

my mistake, it's an m4 build.

> I tried recently and again last night with the eclipse 3 branch but
> was having a lot of problems getting the project recognized. I read
> the paper by Sunghun Kim & Guozheng Ge posted here recently but it
> seemed to be missing important details about the subclipse3 branch.

after checking it out, you should reocompute the project classpaths.
eclipse will correct everything by inserting the right libs for your

> I get errors on all the required plugins and the extension point (in
> core at least) for example. I tried adding the jars from these
> plugins in ECLIPSE_HOME to the libraries in build path properties but
> this had no effect. I'm new to plugin development but have done this
> a few times before and not had this problem - sorry if I've asked a
> bone-headed newbie question.
> Notes:
> - I assume the correct start is to check out
> branches/subclipse-3/core, branches/subsclipse-3/core-windows, and
> branches/subclipse-3/ui as well as trunk/svnClientAdapter as projects
> (using subclipse .81 IIRC)

you don't need svnclientadapter, it's included in core

> - I noticed after it was too late to try again that I had done the
> whole thing under M4 instead of M5, but am I right that this should
> not have caused the problems I was seeing? Could the api have changed
> so significantly between M4/5?

yup, the plugin apis have changed from 4-5, lots of stuff moved (so
it's trivial to fix).

McClain Looney
Received on Thu Dec 11 12:07:03 2003

This is an archived mail posted to the Subclipse Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.