Description Jeff McAffer 2011-04-28 22:05:53 EDT

in i0427

There seems to be a disconnect between the set of features selected in a software site and the set that are discovered/used in the actual target model.  It seems that the most recent version of a given feature is used at various points in the PDE workflows.  As a result, you can get mismatches if the bundlepool contains later versions than are actually indicated by the target definition.

For example, say you define a target that has version 1.3 of some feature.  That all resolves and the various sub features and bundle are downloaded into the bundle pool.  Then you decide the 1.3 sucks and want to use 1.2. After editing the target definition, the versions for 1.2 are downloaded into the bundle pool.  At that this point I seem to recall some relatively promiscuous scanning for features to build the list of feature models.  The end user effect I was just experiencing had (in this example) version 1.3 of the feature being used rather than 1.2.  The user expectation is that 1.3 should not even be part of the model.

After doing a garbage collection (using the hokey add a target, remove a target workflow ;-) the problem went away as only version 1.2 and its prereqs were present in the bundle pool.

While this is bothersome and a bear to figure out, I don't think we should dive into the problem for 3.7 as ti will likely require some non-trivial rethinking of how the feature models are managed in the bundle pooled world.  I'd be happy to see a fix but its not critical for this release.