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

["Bob Foster" <bob@xxxxxxxxxx>]

"Harald Niesche" <harald@xxxxxxxx> wrote in message
news:alnvti$h4d$1@xxxxxxxxxxxxxxxx
> "Bob Foster" <bob@xxxxxxxxxx> wrote in message
> news:alnv0q$ghg$1@xxxxxxxxxxxxxxxx
> > 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.
>
> Exactly which variables are those?

Look at the source properties for plugins you depend on. Those variables.

> The only thing I noticed is that Plugin projects get an incompatible
> .classpath file that can be fixed using "Update Classpath" -- maybe we
> shouldn't have checked the .classpath into CVS?

You get "Update Classpath" to do something useful? The only thing I've ever
seen it do in a plugin project is rip out all the build dependencies,
requiring me to re-add them by hand. (I tried this again in 2.0.1.) What am
I doing wrong?

If there was a quick way to reconstruct the classpath, yes it would be
better not to have checked it in.

Bob