[edgenuity]

I went to upgrade Eclipse to get the latest patches and it failed at the end because of conflicts with MyEclipse 5.1.
I’m running the latest version of Eclipse (3.2.1) with the Callisto options.
When navigating through the entire list of updates I got the following warnings if I proceeded:

“If you continue with the update/install, the resulting configuration will contain duplication conflicts that my cause parts of the product to be unusable. Do you want to continue?”

I of course said no, because I don’t know the consequences.
These are the conflicts:

J2EE Standard Tools (JST) Project:
– Version 1.5.2.v200610070…. in c:/eclipse/
– Version 1.5.2.v20061111 in c:/MyEclipse-5.1/eclipse
Java EMF Model
– Version 1.2.1.v20060815_M… in c:/MyEclipse-5.1/eclipse/
– Version 1.2.1.v20061027_M… in c:/eclipse
Web Standard Tools (WST) Project
– Version 1.5.2.v20061007… in c:/eclipse
– Version 1.5.2.v20061111 in c:/MyEclipse-5.1/eclipse/

Please advise

[support-snjeza]

edgenuity,

MyEclipse 5.1 contains a patched WTP 1.5.2. It won’t work with original WTP.
MyEclipse’s WTP 1.5.2 is compatible with the original WTP and your other applications that require WTP (if you have them) will work correctly with MyEclipse.
It means that you don’t have to update WTP except you want new features.
You can upgrade WTP from Callisto site to a separate location and switch (disable/enable with Help>Software Updates>Manage Configuration) between MyEclipse’s WTP(disable Callisto WTP) and Callisto’s WTP (enable).
When Callisto’s WTP is enabled, MyEclipse won’t work properly.

[edgenuity]

Thanks for the response.
However, WTP is only one component (and it was not in my list of warnings).
I guess the fundamental question, when I get these warnings because of conflict with MyEclipse does that mean I shouldn’t upgrade?

I suppose MyEclipse is bundled/tested with a particular version. Whenever Eclipse releases new libraries/patches I have to wait for MyEclipse to do the same?

[support-snjeza]

MyEclipse uses EMF, GEF and JEM (there are the standard WTP dependencies).
MyEclipse doesn’t change these plugins.
The remaining plugins should be worked properly.

Snjeza

[Scott Anderson]

I suppose MyEclipse is bundled/tested with a particular version. Whenever Eclipse releases new libraries/patches I have to wait for MyEclipse to do the same?

Yes, MyEclipse is built and tested against very particular versions of Eclipse, WTP (WST/JST), EMF, GEF, JEM, etc. Typically, as in the case with MyEclipse 5.1, these are the latest builds available. In order to avoid the update manager warnings in the future, we suggest that you begin with a functional MyEclipse installation then run the update manager on that, rather than starting with Eclipse, WTP, and other tools installed separately and then installing MyEclipse. We go over the reasons and suggest install order in the release announcement here: http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-14982.html

Based on what hte update manager is showing you right now, you’re completely up to date and nothing would be gained by updating further since MyEclipse 5.1 includes the latest builds. If you want to “start fresh” and avoid this in the future, the easiest way to do that is to download and install the “all-in-one” installer from the downloads section. Just plop it down in a new directory, open your existing workspace, and you’ll be good to go.

[Author]

Posts