| commit | f6652fc6e48d412ef6dc919105ed81f3bb3954ef | |
| author | Andrey Loskutov <loskutov@gmx.de> | |
| Thu, 25 Oct 2018 20:56:09 +0000 (25 22:56 +0200) | ||
| committer | Andrey Loskutov <loskutov@gmx.de> | |
| Sat, 27 Oct 2018 22:35:27 +0000 (28 00:35 +0200) | ||
| tree | 0cdfe02984f5187af70d021b61f47efaf9b6c47b | treesnapshot (tar.gz zip) |
| parent | 7f8a7bb4cbee64f710ca530b3d118c4f86d00566 | commitdiff |
Do not trigger JDT UI init in Activator.start()
Activator.hasJavaPlugin() should not trigger JDT UI activation via
Class.forName in start() of EGit UI bundle. This adds JDT UI init
overhead (recursively) to the EGit UI bundle init, and can cause a
bundle activation error due timeout in start().
To check if JDT UI bundle is available, just use Platform.getBundle().
To hook Git template resolvers to JDT UI, use UI job which will do the
work outside of the start() method scope.
Bug: 540487
Change-Id: Ieea5295e52a29582341dbc3caf407db912a516d7
Signed-off-by: Andrey Loskutov <loskutov@gmx.de>
Activator.hasJavaPlugin() should not trigger JDT UI activation via
Class.forName in start() of EGit UI bundle. This adds JDT UI init
overhead (recursively) to the EGit UI bundle init, and can cause a
bundle activation error due timeout in start().
To check if JDT UI bundle is available, just use Platform.getBundle().
To hook Git template resolvers to JDT UI, use UI job which will do the
work outside of the start() method scope.
Bug: 540487
Change-Id: Ieea5295e52a29582341dbc3caf407db912a516d7
Signed-off-by: Andrey Loskutov <loskutov@gmx.de>