RE: [ve-dev] Exception while debugging the VE plugin

[Rich Kulp <richkulp@xxxxxxxxxx>]

Hi,

It means that the org.eclipse.jem.proxy
plugin is not showing up in your project's classpath.

Rich

"Janak Mulani" <janak.mulani@xxxxxxxxx>
Sent by: ve-dev-bounces@xxxxxxxxxxx

06/28/2006 12:31 PM

Please respond to
Discussions people developing code for the Visual Editor project <ve-dev@xxxxxxxxxxx>

To	"Discussions people developing code for the Visual Editor project" <ve-dev@xxxxxxxxxxx>
cc
Subject	RE: [ve-dev] Exception while debugging the VE plugin

Hi Rich,
 
Removing JEM plugins from the
workspace helped. I could start the Swing VE in runtime workbench.
 
But I get the following compilation
error for ULC VE plug-in:
 
The project was not built since
its build path is incomplete. Cannot find the class file for org.eclipse.jem.internal.proxy.core.IBeanProxy.
Fix the build path then try building this project  com.canoo.ulc.visualeditor
Unknown 1151512023706 194
The type org.eclipse.jem.internal.proxy.core.IBeanProxy cannot be resolved.
It is indirectly referenced from required .class files com.canoo.ulc.visualeditor/src/com/canoo/ulc/visualeditor/proxy
ULCWindowProxyAdapter.java line 0 1151512023706 193
Thanks for your help.
 
Best regards,
 
Janak
-----Original Message-----
From: ve-dev-bounces@xxxxxxxxxxx [mailto:ve-dev-bounces@xxxxxxxxxxx]On
Behalf Of Rich Kulp
Sent: Wednesday, June 28, 2006 8:36 PM
To: Discussions people developing code for the Visual Editor project
Subject: Re: [ve-dev] Exception while debugging the VE plugin


Hi, 

How did you import the VE plugins into your workspace? You should be using
Import plugins with Binary with Linked Content for all of the VE/JEM plugins.
I think that would fix the problem. 

The reason it is failing is because it needs to have on the classpath the
jar for org.eclipse.jem.proxy plugin itself, but it was imported and was
no longer a jar. This caused problems because we couldn't find it since
it wasn't there. 

If this doesn't fix it, then remove them as imported entirely. Then we
will definitely find them because they are the actual released jars. What
you lose those is the separation of searching. Now if you say search only
within a plugin/project for something, it will still find things in VE
because under the covers PDE adds the VE jars as direct jars under the
plugin project instead of being shown as pre-reqed jars from a separate
project. This can be annoying when you want to limit a search.

Thanks, 
Rich_______________________________________________
ve-dev mailing list
ve-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ve-dev