Re: Workbench 1.1 start up bomb
- To: mathgroup at smc.vnet.net
- Subject: [mg79523] Re: [mg79453] Workbench 1.1 start up bomb
- From: Adam Berry <adamb at wolfram.com>
- Date: Sat, 28 Jul 2007 05:38:46 -0400 (EDT)
- References: <200707270948.FAA02698@smc.vnet.net> <46AA0B15.6000504@wolfram.com> <46AA3FBF.3050806@math.umass.edu>
Murray Eisenberg wrote: > Thanks. But: > > (1) Exactly what must one do: uninstall 1.0, delete the > .WolframWorkbench folder, also uninstall 1.1, then reinstall 1.1? Or > just uninstall 1.0 and delete the .WolframWorkbench folder? I would suggest uninstall 1.0, delete .WolframWorkbench and then just run 1.1 (no further modification necessary). > > (2) Why doesn't the installer detect this and ask the user to quit and > first uninstall the earlier version? The .WolframWorkbench folder is created by Wolfram Workbench at runtime and not by the installer, hence the installer not detecting this. It is not standard in our products for the installer to talk about a previous version, the Mathematica installers have never done this. > > (3) Why don't the installation instructions for 1.1 -- > > http://support.wolfram.com/workbench/systems/windows/install11.html > > -- mention any of this this? Only a minority of users should encounter this problem when moving from 1.0 to 1.1, hence just a separate FAQ. But that is a sensible suggestion and I will have a link added to the installation instructions along with a comment. > > (4) Why in the first place must there be such a conflict? That folder has some information about certain plugins and their versions, it is created at runtime. So when a newer version opens it looks in that location and if what it has doesn't match up with the newer running version it can cause issues. This is inherited from Eclipse, we will look at working around it. > > (5) Did nobody notice that the protocol is evidently different for > Workbench from that of Mathematica? In the latter, there is little > conflict with an older version when a new version is installed (except > for some error messages about being created in a different version when > Untitled notebooks are opened. Without going into too much detail there are possible places where there can be conflicts between versions of Mathematica besides the notebook version warning, but they are rare just as this one is. I apologize for any inconvenience this caused, and will go ahead and get the FAQs updated. Adam Berry Wolfram Research, Inc > > > Adam Berry wrote: >> Hello, >> >> this is an FAQ, see; >> >> http://support.wolfram.com/workbench/systems/allplatforms/workbenchversionerror.html >> >> >> If you continue to use both 1.0 and 1.1 on this system you may well >> run into this problem again. There really is no reason to keep 1.0, >> and I would recommend removing it and just using 1.1, thanks to the >> workspace system you won't lose any work, and any projects/workspaces >> that you have will just work in the new version. >> >> Thanks, >> >> Adam Berry >> Wolfram Workbench Development Team >> Wolfram Research, Inc >> >> Murray Eisenberg wrote: >>> I installed Wolfram Workbench 1.1 under Windows (leaving a >>> previously installed Workbench 1.0 undisturbed -- I hope!). When I >>> attempted to start it, I got a pop-up window saying, "An error has >>> occurred. See the log file...". >>> >>> The log file begins: >>> >>> !SESSION 2007-07-26 11:09:06.609 >>> ----------------------------------------------- >>> eclipse.buildId=M20060629-1905 >>> java.version=1.5.0_10 >>> java.vendor=Sun Microsystems Inc. >>> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US >>> Command-line arguments: -os win32 -ws win32 -arch x86 >>> >>> !ENTRY org.eclipse.core.runtime 4 0 2007-07-26 11:09:13.390 >>> !MESSAGE FrameworkEvent.ERROR >>> !STACK 0 >>> org.osgi.framework.BundleException: The bundle could not be >>> resolved. Reason: Missing Constraint: Require-Bundle: >>> org.eclipse.equinox.registry; bundle-version="[3.2.0,4.0.0)" >>> at >>> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:294) >>> >>> at >>> org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:329) >>> >>> at >>> org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1037) >>> >>> at >>> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:573) >>> >>> at >>> org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:495) >>> >>> at >>> org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:275) >>> >>> at >>> org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:455) >>> >>> at >>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:189) >>> >>> at >>> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:291) >>> >>> >>> !ENTRY org.eclipse.osgi 4 0 2007-07-26 11:09:13.406 >>> !MESSAGE Bundle >>> initial@reference:file:plugins/org.eclipse.core.runtime_3.2.0.v20060603.jar/ >>> was not resolved. >>> >>> >> >
- References:
- Workbench 1.1 start up bomb
- From: Murray Eisenberg <murray@math.umass.edu>
- Workbench 1.1 start up bomb