[news.eclipse.tools] Re: Runtime uses some obsolete version of my class

[dagaeff@xxxxxxxxx (dagaeff)]

Thank you for the quick answers.

The workaround Andrew McCullough proposed is certainly what I needed; its
far more simpler than refactoring class names two times!

Thierry Dagaeff

Andrew McCullough wrote:


> Yes, it points to the base eclipse plugins in my install (eclipse/plugins)
> directory, and then addition in-development plugins from my workspace.  The
> original poster's question had to do with the Runtime Workbench mysteriously
> holding on to old code.  I have experienced similar problems _occasionally_
> when new plugins are added, either in the workspace or in the install
> directory.  I have no real explanation for it, but clearing out the runtime
> workspace (or using a new one) seems to fix it, so I was advising him to do
> so.  The problem is very rare, and I don't know what causes it.  I'm not too
> worried, though, since I know how to work around it.

> -Andrew

> <SNIP>

> > can you confirm then that teh PDE launcher is pointing to your plugins
> > inside the workspace and teh rest outside ?
> > Or is pointing to only plugins inside the workspace ?
> >
> > Preferences -> plug-in development -> target Platform
> > The plugin path should contain the plguin you develop from the workspace
> > only, so when they change, the runtime uses them....
> >
> > --
> > Christophe Elek
> > Eclipse Project
> > http://www.eclipse.org