Skip to main content
diff options
authorUmair Sair2019-04-14 12:56:24 +0000
committerJonah Graham2019-06-21 17:18:06 +0000
commit15cf76040530e7bf60204bffefa202a99b495eac (patch)
treed7c79464301a96d4c911e4e2526dd9ca00f96656 /build/org.eclipse.cdt.managedbuilder.core/META-INF
parent0ee3822b0467d14393027045cb6e5ff68dfd7a0f (diff)
Bug 546407 Project dependencies are not built in the correct order
Problem: ======== filterConfigsToBuild(..) always filters the configs that are once added to set irrespective if it has been built or not. Consider scenario where there are three project a, b, c and a depends on b & c and b depends on c. When a is built, filterConfigsToBuild(..) returns configs of b and c. Then b starts building and filterConfigsToBuild(..) doesn't return config of c because its already in set. This is wrong and it should return config of c because it is not yet built and b depends on it. Fix: ==== If a referenced config by any project/config is not yet built, filterConfigsToBuild(..) shouldn't filter it. Change-Id: I5fbe77789f14ce3114200998070a7461069c98ab Signed-off-by: Umair Sair <>
Diffstat (limited to 'build/org.eclipse.cdt.managedbuilder.core/META-INF')
1 files changed, 1 insertions, 1 deletions
diff --git a/build/org.eclipse.cdt.managedbuilder.core/META-INF/MANIFEST.MF b/build/org.eclipse.cdt.managedbuilder.core/META-INF/MANIFEST.MF
index 10e12c9038..49db430575 100644
--- a/build/org.eclipse.cdt.managedbuilder.core/META-INF/MANIFEST.MF
+++ b/build/org.eclipse.cdt.managedbuilder.core/META-INF/MANIFEST.MF
@@ -2,7 +2,7 @@ Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: %pluginName
Bundle-SymbolicName: org.eclipse.cdt.managedbuilder.core; singleton:=true
-Bundle-Version: 8.7.0.qualifier
+Bundle-Version: 8.7.100.qualifier
Bundle-Activator: org.eclipse.cdt.managedbuilder.core.ManagedBuilderCorePlugin
Bundle-Vendor: %providerName
Bundle-Localization: plugin

Back to the top