When updating bundles, is the best strategy to update all extant bundles or update one bundle which is a little like an eclipse feature, having dependencies to the rest?
I've been doing the latter but the resulting workflow seems pretty crazy to me. Imagine the following package dependencies: A -> B -> C That is, A is dependent on B, B is dependent on C. A, B and C are all in different bundles. For the sake of discussion, the bundles are also called A, B and C. The package dependencies are declared in the respective manifests for each bundle Now, I am running C and I notice a CNFE. So I add the required package to C's manifest. Bear in mind first of all that this isn't actually an API change and not really a package level code change either, so I'm not 100% sure where that sits in 'semantic versioning', but anyway here's what I do after adding the dependency: 1) Choose an arbitrary package in bundle C and incremement the version 2) In the import for the package chosen in (1) in bundle B, increment the version so the new version will be pulled in upon update. 3) Now increment an arbitrary package in B 4) In the import for the package chosen in (3) in bundle A, increment the version so the new version will be pulled in upon update 5) Increment the version of bundle A so that OBR will update it If I update all extant bundles then I don't need to do this, but how do I remove bundles that are no longer required? Dan
