This repository has been archived by the owner on May 7, 2020. It is now read-only.
model.*.runtime must not use lazy activation #446
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The model.*.runtime bundles must be started automatically, we need them running for ESH. The lazy bundle activation will retain the execution of the activator's start method until a class is accessed first. This will result in not started bundles and missing functionality (e.g. a bundle does not export a package or no one use an exported package). Bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=477075 Signed-off-by: Markus Rathgeb <maggu2810@gmail.com>
kaikreuzer
added a commit
that referenced
this pull request
Sep 10, 2015
model.*.runtime must not use lazy activation
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The model.*.runtime bundles must be started automatically, we need them
running for ESH.
The lazy bundle activation will retain the execution of the activator's
start method until a class is accessed first. This will result in not
started bundles and missing functionality (e.g. a bundle does not export
a package or no one use an exported package).
Bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=477075
Signed-off-by: Markus Rathgeb maggu2810@gmail.com