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

[John Arthorne <john_arthorne@xxxxxxxx>]

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