| commit | 828b8fe5d57fcade708fc276b4cafcc2bb0d59a9 | [log] [tgz] |
|---|---|---|
| author | Matthias Becker <ma.becker@sap.com> | Tue Oct 10 20:45:48 2017 +0530 |
| committer | Vikas Chandra <Vikas.Chandra@in.ibm.com> | Wed Oct 11 14:05:22 2017 +0530 |
| tree | 7c4d92122c4fd52715b80cd5c4c63be82e67265b | |
| parent | 76b65f448ab8caff51b13057b50cfa6d4143ca5f [diff] |
Bug 477578 - PDE activator slows down startup of Eclipse Bug 477578: PDE activator slows down startup of Eclipse The contribution to the org.eclipse.ui.services extension point had the effect that the PDE bundle (and all it's dependencies) where activated already at start up of the platform. In use-cases where PDE is installed but not used (e.g. because one does pure Java development) this is not necessary. As all the bundle activation happens sequentially in the UI thread this directly adds up to the start up time during which the user sees the splash screen. The ImageBrowserView no longer uses a service to communicate the selected image to the SaveToWorkspace command handler. As the view and the command handler are anyway hardly coupled the decoupling via a service does not bring any advantages but only bring the performance penalty at start up. Change-Id: I183d1a38d99c6bbf9f2cf3220125bf8810588fa4 Signed-off-by: Matthias Becker <ma.becker@sap.com>
Thanks for your interest in this project.
The PDE project the Eclipse tooling to develop plug-ins and OSGI bundles.
Website: https://www.eclipse.org/pde/
Contributions to PDE are most welcome. There are many ways to contribute, from entering high quality bug reports, to contributing code or documentation changes. For a complete guide, see the [How to Contribute] 1 page on the team wiki.
Information regarding source code management, builds, coding standards, and more.
Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).
This project uses Bugzilla to track ongoing development and issues.
Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!
Contact the project developers via the project's “dev” list.