Skip to main content
diff options
authorThomas Watson2019-04-09 14:13:14 -0400
committerThomas Watson2019-04-12 09:58:21 -0400
commit2e8fc7a7f648e3ad325e55863aca098c8e108db6 (patch)
tree572bb72a7f16728e84a0f3411c22700e0135d8fc /bundles/org.eclipse.osgi/pom.xml
parente98581771affe7d6ae47902670bacc572b0a9e75 (diff)
Bug 540507 - parallel activation of bundles from framework start-level
By default the framework start-level implementation activates all bundles that have the same start-level in sequential order using the bundle ID (install order) to determine the order the bundles are started from a single thread. A new configuration option is added equinox.start.level.thread.count that is set to 1 by default. This will cause the framework to continue with the behavior of activating all bundles with a single thread. If equinox.start.level.thread.count is set to -1 then the framework will use an executor with the number of threads == to java.lang.Runtime.availableProcessors() to activate the bundles in parallel. This means that the order the bundles with the same start-level are activated becomes random. The equinox.start.level.thread.count config setting can also be set to a value > 1 to give an explicit value for the number of threads to use (instead of using java.lang.Runtime.availableProcessors() to determine the number) Change-Id: Ifcf6f18b762bcb114f8f8c75630fdca0cb79a24c Signed-off-by: Thomas Watson <>
Diffstat (limited to 'bundles/org.eclipse.osgi/pom.xml')
1 files changed, 1 insertions, 1 deletions
diff --git a/bundles/org.eclipse.osgi/pom.xml b/bundles/org.eclipse.osgi/pom.xml
index 92a400413..48467d543 100644
--- a/bundles/org.eclipse.osgi/pom.xml
+++ b/bundles/org.eclipse.osgi/pom.xml
@@ -19,7 +19,7 @@
- <version>3.13.400-SNAPSHOT</version>
+ <version>3.14.0-SNAPSHOT</version>

Back to the top