[rossi]

Hi,

I have a clean install of Eclipse 2.1.2 with MyEclipse 2.7 RC1.
When testing for Available Updates via “New Updates”, Eclipse
suddenly finds 2 candidates:

1) Eclipse Project SDK (Windows) 2.1.2
2) MyEclipse Enterprise Workbench 2.6.100

The Eclipse update is bogus: it wasn’t there before installing
MyEclipse and trying to install this update does nothing.
Next try, it is still flagged as available.

The MyEclipse doesn’t make sense either, since I already
have 2.6.100 (aka 2.7 RC1) installed.

Irritating thing. Does this break Update functionality?
What will happen when eclipse 2.1.3 is released (if ever)?

-rossi

[Riyad Kalla]

Hey Rossi,
This has come up before and Scott pointed out that this does interfere somewhat with the Eclipse update process, but necessary so as MyEclipse isn’t just a simple plugin. He also mentioned that the ME team is good at staying ontop of Eclipse updates so you won’t need to worry, BUT I do not know if that means future Eclipse updates we be deployed as part of ME through the update manager or what… I’m sure Scott can explain this better.

I agree that it is a bit overbearing for it to stand in the way of the update system like this, hopefully a fix with come with Eclipse 3.0 (new design?)

[Scott Anderson]

Rossi,

There is a minor issue here, as Riyad pointed out. The Eclipse update manager was always a bit of an odd beast, which is why it’s being completely rewritten for 3.0. What you’re seeing is a combination of a couple of things. First, you’re seeing the Eclipse 2.1.2 update because we ship a mildly tweaked version of a few of the JDT plugins so we can enable source-level JSP debugging. This confuses the update manager, even though we properly number them as later versions. This will go away in the 3.0 timeframe as our changes become part of platform and the update manager is overhauled.

The second issue, that you’re still showing RC1 as a pending update is also easily explainable. Eclipse doesn’t think there is any way to install anything except through the update manager. Installing with a double-click installer, while fully supported by Eclipse, isn’t fully supported by the update manager. As a result, the update manager isn’t notified that the update took place. However, I updated through the update manager on one of my instances and now the 2.7 RC1 update no longer shows that it’s available. That is, it works properly as long as the update manager is used for the upgrades.

That’s a long explaination but hopefully it lets you know why it is as it is and how it will get better with the improved update manager in 3.0

–Scott
MyEclipse Support

[rossi]

Thanks for the explanation. My first impressions of MyEclipse are pretty good (I like the JSP and XML editors), but I still have to play with xdoclet and struts support. Coming from a long-time love&hate relationship with JBuilder, eclipse plus your extensions take some time to get used to I suppose.

[Riyad Kalla]

Yes but hopefully it will be a learning process devoid of hate 🙂

[Scott Anderson]

eclipse plus your extensions take some time to get used to I suppose.

Eclipse alone takes a good while to get used to. Especially coming from JBuilder as Eclipse is just different. Hopefully the changeover won’t be too painful. When it starts getting difficult, remember that we’re here to help.

–Scott
MyEclipse Support

[Author]

Posts