RE: [ve-dev] VE in PDE

[Rich Kulp <richkulp@xxxxxxxxxx>]

Hi,

That's the major difference in packaging
between the two.  It seems to be having trouble finding the classes
to give to the remote vm or to compile for templates when the plugins are
imported. We just haven't had the time to figure out why since it can work
if you don't import.

Rich

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

07/10/2006 10:39 AM

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] VE in PDE

Hi Rich,
 
This is different from VE 1.1/Eclipse
3.1.
 
In all earlier VE/Eclipse versions
we alway imported plug-ins in the workspace and it used to work.
 
So what has changed between 1.1/3.1
and 1.2/3.2 is the way plug-ins are packaged (dir v/s jars). Is this reight?
 
Thanks and regards,
 
Janak
-----Original Message-----
From: ve-dev-bounces@xxxxxxxxxxx [mailto:ve-dev-bounces@xxxxxxxxxxx]On
Behalf Of Rich Kulp
Sent: Monday, July 10, 2006 4:20 PM
To: Discussions people developing code for the Visual Editor project
Subject: Re: [ve-dev] VE in PDE


Hi, 

Don't import the plugins. Just make sure they are in the PDE's target platform.
We haven't done any testing with it imported like that. I think it has
to do with the fact that the plugins are packaged as jars instead of directories.
It can't find some of the necessary files if the plugins are imported.

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