[news.eclipse.tools] Re: 2.0.1 feature change

[Peter Manahan <manahan@xxxxxxxxxx>]

Sounds like you are not using binary projects. I don't ever use the CVS 
version of eclipse I tend to use stable and integration builds. Binary 
projects tend to shield you from changes like you mention as well as 
from fragments changes to os things like swt.

For me it works like this. I may have misunderstood the problem though, 
if so hopefully this is helpful to someone even if I am way off base.

From scratch
1) Download eclipse sdk.
2) File->Import->External Plugins and Fragments. Next
3) select choose from runtime workbench etc
4) pick the plugins you want from this page and then select "add 
required plugins". Finish
5) Change the build paths in your projects from using variables to using 
the plugin projects instead.

After I updated to 2.0.1 I deleted all my currently loaded binary plugin 
projects and reimported from the new list. I didn't have to change my 
own projects at all.  Seems to work ok.


Hope this helps.
Peter

Bob Foster wrote:

> Thanks. This seems like my day to get useful pointers.
>
> Just one thing, tho. "The most common procedure for plugin developers" must
> refer to plugin developers within OTI. But outside OTI, one really wants to
> build on released versions, for which, correct me if I'm wrong, means using
> the source that is provided with the release, CVS having moved on.
>
> The actual origin of this thread arises from my dissatisfaction with the
> release dependency involved in using release source code. To wit: a) the
> source code paths still have version numbers in them, even with variables,
> and b) even if this were fixed, updates don't ship all source, just the
> updated source, so when the variable changes some source "drops out".
>
> Is there still something I'm missing?
>
> Bob
>
> "John Arthorne" <john_arthorne@xxxxxxxx> wrote in message
> news:3D810E86.6070509@xxxxxxxxxxx
>
> > The most common procedure for plugin developers is to import all plugins
> > that your plugin depends on into your workspace.  This is done using the
> > "import external plugins" tool.  That way, the build path refers to
> > projects, not exteral paths, so you are not affected by an upgrade that
> > changes paths.  This also means that you can checkout source for those
> > projects from CVS without changing any build paths.  There is support in
> > eclipse views to automatically hide binary projects (imported projects
> > without source), which makes this approach less intrusive than it seems.
> > As a bonus, the search engine behaves better for binary projects than
> > for external jars on the build path.
> > -
> >
> >
> > Bob Foster wrote:
> >
> >
> > > 2.0.1 introduces new variables to your classpath, making your projects
> > > incompatible with 2.0. So the first time you check a project in, your
> whole
>
> > > team needs to update to 2.0.1.
> > >
> > > After some thrashing around trying to discover some benefit in this
> change
>
> > > (it didn't fix the source version problem, but it sure made it more
> > > complicated) I have regretfully backed up to 2.0.
> > >
> > > This is a bit more of a feature change than I expected in a bug fix
> release.
>
> > > Is this SOP for Eclipse?
> > >
> > > Bob