- This topic has 7 replies, 6 voices, and was last updated 20 years, 2 months ago by
.
-
Posts
-
Operating system/version: Win2K
Eclipse version/build id: 3.0.0 200406251208
Eclipse freshly installed for MyEclipse?: Yes
MyEclipse version: 3.8.1 Build id: 200408201200-3.8.1
JDK version: 1.4.2_05-b04
JDK version are you using to launch your application server: 1.4.2_05-b04
What application server are you using: n/a
Are there any errors in the Eclipse log?: YesEclipse Visual Editor 1.0 RC3 requires the plugin com.ibm.wtp.common.util version 1.0.1.
MyEclipse installs this plugin in version 1.0.0 as com.ibm.wtp.common.util 13.8.1.
Visual Editor crashes with a NoClassDefFoundError.
As temporary bypass I have replaced the jar file contained in the plugin directory and added a subdirectory contained in the new version of the util plugin.
This gets VE working.Would it not be easier if helper plugins like the one above are installed by MyEclipse using the original version number instead of the 13.8.1?
Compatibilty with other Eclipse extensions is significantly reduced.I believe the issue is that this plugin originated in the IBM WSAD codebase and was copied to both the the VE and the WTP projects. Those projects modified the version number to their own purpose. We don’t do anything special with this plugin so I’m assuming the version number is as defined by the WTP project. We’ll look further and provide a definitive response.
Michael,
Yes, the elements are all part of IBM’s donation to the webtools project originating from WSAD.
Following to the documentation the plugin is part of the JEM component which is shared between VE and the webtools.
JEM was updated to 1.0.1.I could not locate an independent download or update for JEM, upgrades are only installed through VE or webtools installs.
The hiccup is caused by the MyEclipse attached version of 13.8.1 to the 1.0.0 level of the plugin.
This hides the existence of the 1.0.1 installed as part of VE.
Without this override the plugin loading would work nicely I guess.@joshdmoore wrote:
I dont understand what the fix was. Can someone explain it better.
I guess the fix is in 3.8.2, you should upgrade to that. There is one known reason I am aware of (which of course does not mean, that there are no other reasons) why not to upgrade to 3.8.2 is if you use JBoss 4.0.RC versions and you cannot upgrade to JBoss 4.0 GA.
Regards,
Robert
I dont understand what the fix was. Can someone explain it better.
Josh, the problem was that we inadvertently changed the plugin version number of two of IBM’s binary plugins which kept updated versions from VE from loading properly. The build issue has been addressed in 3.8.2 by resetting the plugin versions to their original level.
