- This topic has 5 replies, 2 voices, and was last updated 19 years, 7 months ago by
.
-
Posts
-
After adding MyEclipse to 3.1RC2 the Visual Editor (VE) no longer works. Can anyone validate this? I have a barebones installation of Eclipse.
Thanks
Tek
If that’s the case (we don’t test with VE), then it’s likely because both VE and MyEclipse use code from other Eclipse projects and one of the products is pulling in a version that is incompatible with the other.
Thanks for the quick response.
If I need to use VE and MyEclipse together then what should I do? I’d hate to become a VE developer to determine what is broken. 🙂
Do you have any future plans to test MyEclipse with VE?
Thanks
That’s a tough one. I’d look at what plugins are the same under both installations and then systematically remove any duplicates from one of them. For example, if both MyEclipse and VE contain org.eclipse.emf or something, then delete those plugins from the MyEclipse install and then restart eclipse with the -clean option to cause all plugins to reload. Please bear in mind that this configuration won’t be supported and you might break something in MyEclipse getting VE to work. But, that’s the basic technique. Oh, and instead of ‘deleting’ the plugins, you might just move them to another location outside the installation in case you want to put them back.
I do not want to be a pest, however if it turns out that VE and MyEclipse both share different versions of org.eclipse.emf.* (which I know VE does, not sure of MyEclipse), what is the best way to approach this problem from a distribution point of view? We have a Rich, Thin Java Client development product, and we want to build on the features of MyEclipse and VE. If we can not get these two products to co-operate out of the box, then even though we are able to patch something together, we will be at a loss to explain that to our end users…
With Eclipse 3.1RC2 I’m using the latest VE and MyEclipse builds , I would hate to wait until there is an ‘eclipse’ and 2 products’ dependencies catch / match up.Normally, the Eclipse plugin loader handles ambiguity like this by using the plugins with the most recent version number. Unfortunately, the EMF team has been releasing drops with the same version number for several months, so it gets down to “build times” and such, which can’t be determined by the plugin loader. For 4.0M2, I know we updated GEF and Draw2D to be the absolute latest, but EMF is likely a month or two old. Given that, I’d imagine that the one in VE is newer and would likely be backward compatable with what we use. So, I’d say try using VE’s EMF plugins rather than ours and see if starting with -clean after removing them resolves the issue.
Going forward, I’ve added a PR to update to the latest version of EMF when we ship the next release.
