[jccartwright]

Hello,

I ran the “Search for updates of the currently installed features” this morning on my eclipse 3.2/ME 5.0.1/callisto installation, and was warned of a conflict between the most recent visual editor (v1.2.1) and the visual editor installed w/ ME (v1.2.0).

Is this a problem? Is there a forthcoming release of ME that will include the new visual editor version?

Thanks!

— john

[Riyad Kalla]

John,
My guess is that the conflict is not with the visual editor itself, but it’s dependencies (we don’t plan on shipping VE to the best of my knowledge, but we do share a lot of the same dependencies on EMF/GEF, etc.). If that’s not the case can you copy-paste the entire error here for me?

[jccartwright]

Hi Riyad,

yes, you’re correct, but my question is essentially the same – there seems to be a conflict between a lower-level component shipped w/ MyEclipse and that currently available. I have a screenshot of the error, but I can’t copy the text. May I send you the image?

Thanks!

— john

[Riyad Kalla]

Sure, you can PM it to me, just click the PM button under my name and attach it to that message. The problem is most likely that VE wants to upgrade EMF/GEF in order for VE 1.2.1 to work, but that would cause MyEclipse to potentially die as those libraries are dependencies of MyEclipse, and if they are upgraded out from under ME’s feet, it could stop working with compatability problems.

Unfortunately there is still the issue of “dll hell” in the Eclipse world when it comes to things like this.

[Author]

Posts