[sofistek]

There is a fix, in eclipse, for an eclipse compiler bug that causes me problems when testing from the IDE. The fix is in eclipse 3.6M6. I tried installing MyEclipse (8.0, from the downloadable archive) on top of that eclipse development release but the installation complains about dependencies. In particular, it says:

Cannot complete the install because one or more required items could not be found.
  Software being installed: MyEclipse Web Tools Integration 8.0.0.me200911192202-7k7EFkHFDHXtTR_jTY6UXdo2_0DI (com.genuitec.myeclipse.webtools.feature.group 8.0.0.me200911192202-7k7EFkHFDHXtTR_jTY6UXdo2_0DI)
  Missing requirement: Structured Source JSP Model 1.2.203.me200911192043 (org.eclipse.jst.jsp.core 1.2.203.me200911192043) requires 'bundle org.eclipse.jdt.core [3.4.0,3.6.0)' but it could not be found
  Cannot satisfy dependency:

From the eclipse installation details, I have org.eclipse.jdt.core 3.6.0.v_A39, but can’t find any mention of org.eclipse.jst.jsp.core.

Is there a way to install MyEclipse on eclipse releases above what MyEclipse is based on? If not, that might seem rather limiting. Even MyEclipse 8.5M2 is based only on eclipse 3.5.1, when the latest release version of eclipse is 3.5.2. I realise that it might need certain features of eclipse at a particular release level but surely later releases of eclipse should support MyEclipse?

I’d appreciate a response on this as the bug is really a bit of a pain (I need to do an external build to run the software I’m testing, rather than running directly from the IDE).

[support-joy]

sofistek,

Please note that ME 8.0 is based on Eclipse Classic 3.5.1 and not 3.6(http://myeclipseide.com/index.php?name=Downloads&req=viewsdownload&sid=36). Please install ME 8.0 on top of Eclipse Classic 3.5.1.
Similartly ME 8.5 is based on Eclipse classic 3.5.2
I am afraid ME cannot be installed currently on Eclipse 3.6. 3.6 will be supported on ME 9.x.

[sofistek]

@support-joy wrote:

sofistek,
Please note that ME 8.0 is based on Eclipse Classic 3.5.1 and not 3.6(http://myeclipseide.com/index.php?name=Downloads&req=viewsdownload&sid=36). Please install ME 8.0 on top of Eclipse Classic 3.5.1.
Similartly ME 8.5 is based on Eclipse classic 3.5.2
I am afraid ME cannot be installed currently on Eclipse 3.6. 3.6 will be supported on ME 9.x.

Thanks for responding. Two points. Firstly, your website for downloading 8.5M2 (or at least the standard edition) says “be sure Eclipse 3.5.1 Classic is installed”, not 3.5.2. However that’s largely irrelevant to my main problem. So my second point it that I already have 8.0 installed (from the all-in-one download) but I thought it was very clear from my post that my reason for wanting to install on top of eclipse 3.6M6 is because of a bug in earlier versions of eclipse that causes me problems when testing my code from the IDE. So suggesting I install eclipse 3.5.1 or 3.5.2 is not going to help me at all.

Are you saying that any particular release of MyEclipse will only ever work with a particular release of eclipse, and not later releases? If so, this seems very limiting, given my situation. It is similar to probably the main criticism of IBM Visual Age for Java, many years ago, which was that developers could not run later releases of java than the one that came with Visual Age (though, in that case, it was because IBM needed to produce their own version of the JVM).

So, if your answer is “yes”, I’ll either have to live with the eclipse bug, until release 9, in the 3rd quarter (possibly), use another IDE (I’d recently moved back to MyEclipse from NetBeans) or use eclipse without MyEclipse but with other plugins. None of those options seems very satisfactory. Which do you suggest I take?

[Brian Fernandes]

Let me clear things up. MyEclipse 8.5M1 and M2 are based on 3.5.1, but MyEclipse 8.5 GA (due this week) will be based on Eclipse 3.5.2.

MyEclipse 8.5 (GA) has a large number of components that are specifically based on Eclipse 3.5.2. We cannot simply remove the upper limit on this restriction as trying to run with later versions of Eclipse will require a later version of integrated components like DTP and WTP, where, unless we specifically write an integration for that version, most of MyEclipse will be defunct.

While I do understand your problem, I’m afraid that we cannot open up the restrictions as it will lead to a completely broken product. On the 3.6 train, we will be releasing a milestone build of MyEclipse 9 as close to the Helios final release as possible, likely a month or less after.

Sorry I could not be of more help.

[sofistek]

OK, Brian. I’m not sure I understand why later versions of DTP and WTP don’t support use of earlier versions of those frameworks but, that would be a large limitation to use of something like MyEclipse and my situation is a perfect example of why.

I’m going to have to seriously consider other options for my IDE, so that I can take advantage of latest software, especially bug fixes. I know you bring out new releases fairly frequently but this means I may have to live with bugs, that have been fixed, for many months after the fix is available. That seems very restrictive, to me.

[Brian Fernandes]

To clarify further, we don’t simply bundle the version of WTP (or DTP) that you can get from the downloads page at eclipse.org. We base our integration on the most recent stable version which is then significantly modified to several fix bugs and integrate seamlessly with MyEclipse. So MyEclipse depends on a modified version of WTP, something we would have to create for each Eclipse (and hence WTP / DTP /etc.) release. I understand your needs, but the only way we can get you on the latest version of Eclipse is to actually create a specific release for that version – something we are working on improving on the speed front, but which is not available at this time.

Typically JDT bugs are ported back to previous Eclipse versions depending on technical feasibility, importance and the number of users affected by that bug; of course, a release in the previous stream must also be due – e.g. 3.5.2. So this is not a situation that we run into often.

Thanks for letting us know this affects you, that will help us prioritize.

[sofistek]

Thanks for the clarification. I’m sympathetic to how you feel you need to operate, though if you are fixing bugs in open source software, for your release, I’d ask if it’s possible to release those fixes to the open source projects affected (indeed, isn’t that a requirement of open source)?

In any case, the bug that was fixed in eclipse had hit me for long enough for me to decide to go back to just using eclipse, for now. I’m not doing EE or Web development, at the moment, so the only MyEclipse tool that I think I’d really need is Matisse. I may start MyEclipse on the rare occasion that I use that editor, though I’m more likely to fire up NetBeans, as that is what my colleagues use (my workspace can operate as eclipse projects or NetBeans projects).

[Brian Fernandes]

The mods we make are regularly released here for each GA release: http://www.myeclipseide.com/module-htmlpages-display-pid-318.html

Of course, not all fixes are picked up and a significant number of changes are not “fixes” but modifications to help MyEclipse integrate with these tools, these will never be picked up as they are very ME specific.

Understand your needs – we are moving to a more frequent release model (for milestones) so perhaps in the future such builds with ME will be available; nothing in the near term though.

Thanks again for asking.

[Author]

Posts