Hi Wendell,
I hit this same issue when installing the latest WTP milestone build.
Removing WTP and starting Eclipse with -clean (because it *totally*
hosed my workspace) made everything better. It seems to be either a WTP
issue or an eclipse issue. Removing the persistent property filter from
the popupMenus extension 'fixed' the problem. Since the actions come
back when webtools is uninstalled, the property *is* there but something
in WTP is causing the tester to fail.
cheers,
Brock
Wendell Beckwith wrote:
> This thread,
> http://subclipse.tigris.org/servlets/ReadMsg?list=3Dusers&msgNo=3D5914
> <http://subclipse.tigris.org/servlets/ReadMsg?list=3Dusers&msgNo=3D5914>,
> details
> a problem I have and I opened up an eclipse issue,
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=3D130893, on it but can
> any dev
> validate whether this is a Subclipse or WTP issue? The only reason I
> include Subclipse is that it may be dealing with another eclipse 3.2 API
> rule update similar to how locking the workspace when checking out a
> project
> had to be updated.
>
> Wb
Received on Fri Mar 10 14:03:08 2006