| Summary: | Utils.isRunning() makes an invalid assumption about the system bundle state | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Thomas Watson <tjwatson> | ||||
| Component: | Update (deprecated - use Eclipse>Equinox>p2) | Assignee: | Platform-Update-Inbox <platform-update-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | d.zinato | ||||
| Version: | 3.6 | ||||||
| Target Milestone: | 3.6 M7 | ||||||
| Hardware: | PC | ||||||
| OS: | Mac OS X - Carbon (unsup.) | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | 309261 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Thomas Watson
Created attachment 165006 [details]
patch
Here is the fix.
Thanks Tom, fix released. It's dubious that we even need to perform this test but won't bother removing it at this point. Here is the only reference to this method: // TODO this test is not really needed any more than any plugin has // to test to see if the runtime is running. It was there from earlier days // where startup was much more disjoint. Some day that level of decoupling // will return but for now... if (!Utils.isRunning()) throw new Exception(Messages.ConfigurationActivator_initialize); John, this fix did not get tagged for the I-Build. As a result update.configurator will not start with the latest build. *** Bug 312400 has been marked as a duplicate of this bug. *** |