- This topic has 6 replies, 2 voices, and was last updated 20 years, 7 months ago by Riyad Kalla.
-
AuthorPosts
-
IvanMemberI previously had a working Eclipse 2.1.3 environment with MyEclipse 2.7GA. I wanted to upgrade to MyEclipse 3.7.2 so I had to uninstall the existing MyEclipse in order to first upgrade Eclipse (which I think I did successfully by deleting the link file in eclipse, then removing all the perspectives, and deleting the MyEclipse directory). Then I downloaded Eclipse 3.08M and extracted the files into the existing Eclipse directory structure. When I tried to start the Eclipse app, it fails and I get a dialog telling me that a configuration log was created. The log contains the following text below… what can I do to fix this?
!SESSION Apr 12, 2004 09:53:55.681 ———————————————
java.version=1.4.2_03
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
!ENTRY reference:file:c:/eclipse/plugins/org.eclipse.osgi.services_3.0.0/ 0 0 Apr 12, 2004 09:53:55.681
!MESSAGE FrameworkEvent.ERROR
!STACK 0
org.osgi.framework.BundleException: The bundle could not be resolved. Reason: probably another version has been chosen
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:391)
at org.eclipse.osgi.framework.internal.core.Bundle.resume(Bundle.java:377)
at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:971)
at org.eclipse.osgi.framework.internal.core.StartLevelImpl.resumeBundles(StartLevelImpl.java:565)
at org.eclipse.osgi.framework.internal.core.StartLevelImpl.incFWSL(StartLevelImpl.java:468)
at org.eclipse.osgi.framework.internal.core.StartLevelImpl.doSetStartLevel(StartLevelImpl.java:269)
at org.eclipse.osgi.framework.internal.core.StartLevelImpl.launch(StartLevelImpl.java:239)
at org.eclipse.osgi.framework.internal.core.SystemBundle.resume(SystemBundle.java:166)
at org.eclipse.osgi.framework.internal.core.Framework.launch(Framework.java:405)
at org.eclipse.osgi.framework.internal.core.OSGi.launch(OSGi.java:51)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:202)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:115)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.core.launcher.Main.basicRun(Main.java:267)
at org.eclipse.core.launcher.Main.run(Main.java:692)
at org.eclipse.core.launcher.Main.main(Main.java:676)
!ENTRY reference:file:c:/eclipse/plugins/org.eclipse.osgi.util_3.0.0/ 0 0 Apr 12, 2004 09:53:55.712
!MESSAGE FrameworkEvent.ERROR
!STACK 0
org.osgi.framework.BundleException: The bundle could not be resolved. Reason: probably another version has been chosen
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:391)
at org.eclipse.osgi.framework.internal.core.Bundle.resume(Bundle.java:377)
at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:971)
at org.eclipse.osgi.framework.internal.core.StartLevelImpl.resumeBundles(StartLevelImpl.java:565)
at org.eclipse.osgi.framework.internal.core.StartLevelImpl.incFWSL(StartLevelImpl.java:468)
at org.eclipse.osgi.framework.internal.core.StartLevelImpl.doSetStartLevel(StartLevelImpl.java:269)
at org.eclipse.osgi.framework.internal.core.StartLevelImpl.launch(StartLevelImpl.java:239)
at org.eclipse.osgi.framework.internal.core.SystemBundle.resume(SystemBundle.java:166)
at org.eclipse.osgi.framework.internal.core.Framework.launch(Framework.java:405)
at org.eclipse.osgi.framework.internal.core.OSGi.launch(OSGi.java:51)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:202)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:115)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.core.launcher.Main.basicRun(Main.java:267)
at org.eclipse.core.launcher.Main.run(Main.java:692)
at org.eclipse.core.launcher.Main.main(Main.java:676)
!ENTRY System Bundle 0 0 Apr 12, 2004 09:53:55.712
!MESSAGE FrameworkEvent.ERROR
!STACK 0
org.osgi.framework.BundleException: Exception in org.eclipse.osgi.framework.internal.core.SystemBundleActivator.start()
at org.eclipse.osgi.framework.internal.core.BundleContext.startActivator(BundleContext.java:1009)
at org.eclipse.osgi.framework.internal.core.BundleContext.start(BundleContext.java:971)
at org.eclipse.osgi.framework.internal.core.StartLevelImpl.resumeBundles(StartLevelImpl.java:545)
at org.eclipse.osgi.framework.internal.core.StartLevelImpl.incFWSL(StartLevelImpl.java:468)
at org.eclipse.osgi.framework.internal.core.StartLevelImpl.doSetStartLevel(StartLevelImpl.java:269)
at org.eclipse.osgi.framework.internal.core.StartLevelImpl.launch(StartLevelImpl.java:239)
at org.eclipse.osgi.framework.internal.core.SystemBundle.resume(SystemBundle.java:166)
at org.eclipse.osgi.framework.internal.core.Framework.launch(Framework.java:405)
at org.eclipse.osgi.framework.internal.core.OSGi.launch(OSGi.java:51)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:202)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:115)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.core.launcher.Main.basicRun(Main.java:267)
at org.eclipse.core.launcher.Main.run(Main.java:692)
at org.eclipse.core.launcher.Main.main(Main.java:676)
Nested exception:
java.lang.IllegalStateException
at org.eclipse.osgi.framework.internal.defaultadaptor.DefaultAdaptor.frameworkStart(DefaultAdaptor.java:776)
at org.eclipse.core.runtime.adaptor.EclipseAdaptor.frameworkStart(EclipseAdaptor.java:185)
at org.eclipse.osgi.framework.internal.core.SystemBundleActivator.start(SystemBundleActivator.java:62)
at org.eclipse.osgi.framework.internal.core.BundleContext$1.run(BundleContext.java:992)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.framework.internal.core.BundleContext.startActivator(BundleContext.java:988)
at org.eclipse.osgi.framework.internal.core.BundleContext.start(BundleContext.java:971)
at org.eclipse.osgi.framework.internal.core.StartLevelImpl.resumeBundles(StartLevelImpl.java:545)
at org.eclipse.osgi.framework.internal.core.StartLevelImpl.incFWSL(StartLevelImpl.java:468)
at org.eclipse.osgi.framework.internal.core.StartLevelImpl.doSetStartLevel(StartLevelImpl.java:269)
at org.eclipse.osgi.framework.internal.core.StartLevelImpl.launch(StartLevelImpl.java:239)
at org.eclipse.osgi.framework.internal.core.SystemBundle.resume(SystemBundle.java:166)
at org.eclipse.osgi.framework.internal.core.Framework.launch(Framework.java:405)
at org.eclipse.osgi.framework.internal.core.OSGi.launch(OSGi.java:51)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:202)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:115)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.core.launcher.Main.basicRun(Main.java:267)
at org.eclipse.core.launcher.Main.run(Main.java:692)
at org.eclipse.core.launcher.Main.main(Main.java:676)
!ENTRY org.eclipse.osgi Apr 12, 2004 09:53:55.837
!MESSAGE Startup error
!STACK 1
java.lang.IllegalStateException: Bundle reference:file:c:/eclipse/plugins/org.eclipse.osgi.services_3.0.0/ was not resolved
at org.eclipse.core.runtime.adaptor.EclipseStarter.loadBasicBundles(EclipseStarter.java:391)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:208)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:115)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.core.launcher.Main.basicRun(Main.java:267)
at org.eclipse.core.launcher.Main.run(Main.java:692)
at org.eclipse.core.launcher.Main.main(Main.java:676)
Riyad KallaMemberiva030,
There is not directly upgrade path between 2.x series of Eclispe and 3.x series of Eclipse. If you want to run Eclipse 3, you need to erase your exist Eclipse installation, or unzip Eclipse 3.0 to a new location. Then you need to run it (allowing it to create a new workspace for 3.0), close it, then install MyEclipse.I believe what you did here won’t work as you have overwritten Eclispe 2 with 3, which in and of itself shouldn’t work, but MAY work… however there is still the issue of the plugin cache and workspace data which is all specific to Eclipse 2.x. If you notice that the exceptions you are getting has nothing to do with MyEclipse but are problems with the fundamental Eclipse platform trying to load incorrect plugin data.
Keep in mind that until 2.8, there will be no functional difference between MyEclipse 2.x and MyEclipse 3.x, so if you need a stable environment, stay with Eclipse/MyEclipse 2.x.
IvanMemberIf I have saved configurations (from before I uninstalled myEclipse2.x and extracted Eclipse 3 over the Eclipse 2 version), would I be able to restore from those back to exactly what I had? If so how?
IvanMember…or what is the easiest way to get back to an Eclipse/MyEclipse 2.x config?
Riyad KallaMemberIf you have your preferences exported and any other information, the easiest/cleanest way is to:
(translate the paths I give to whatever you would prefer, I’m just giving the general-case guide)-
1) Download Eclipse 2.1.3 SDK again, unzip to C:\Eclipse\2.1.3 <– this is done so you could have C:\Eclipse\3.0M8 for another install, people seem to like doing this.
2) Download MyEclipse 2.7.1 again, unzip to C:\MyEclipse\2.7.1 <– again for the same reason as above
3) Run Eclipse 2.1.3, then shut it down.
4) Create the C:\Eclipse\2.1.3\links file per the MyEclipse Manual Install instructions, that poitns to your MyEclipse install
(contents of that link file will be: path=C:\\MyEclipse\\2.7.1)
5) Run Eclipse again, hit OK to finalize install of MyEclipse
6) Now go to Preferences, and import all your settings. Double check that you have a JDK setup (not a JRE) so you can run you app server from MyEclipse
7) Double check your settings quickly (and templates, keybindings, etc.) to make sure they are all back to normal.
8) That’s it!So a 100ft overview of what I outlined above is “Remove Eclipse 3, reinstall Eclipse 2 and MyEclipse 2”. Its a good thing you saved the preferences, that makes the job much easier.
I’m sorry you had to run into this problem, from a user perspective its hard to tell if you can safely upgrade from Eclipse 2 to 3 or if its a major upgrade (like Windows 98 to Windows XP). I hope this works for you and you are back up and running soon.
IvanMemberThanks… it appears that I’m back up and running now. I truly like the MyEclipse product, but I have experienced much confusion regarding the different versions, and which to use. It may be useful to have the site clearly suggest which version is recommended, and the reasons/benefits/drawbacks for using the other versions (with regard to BOTH the base Eclipse and MyEclipse components). Part of the problem is that the Home page had an item in the News & Updates section stating that… “New MyEclipse Release Now Supports Eclipse 3.0 M8”. I assumed that this was the recommended version with the latest features, so I proceeded to mess things up.
Out of curiosity, when do you expect 2.8 to be available? And when can we expect to be able to safely upgrade to the 3.x versions of both Eclipse/MyEclipse?
Riyad KallaMember… “New MyEclipse Release Now Supports Eclipse 3.0 M8”. I assumed that this was the recommended version with the latest features, so I proceeded to mess things up.
I think you have a very good point here and I will pass it by the support/web team to see if there is a natural way for us to make this more clear with explinations of both setups.
Out of curiosity, when do you expect 2.8 to be available?
We are in major-tool-development mode right now, so I believe we are hoping for a internal beta at the end of May and a release in late June I think. Also based on Eclipse release Timeline they are hoping for a late June release as well, although I noticed in the bug tracker (Eclipse) that a new Milestone (M10) was added, but it wasn’t accounted for in the project release timeline last I checked, so they might release later than June.
-
AuthorPosts