Community
Participate
Working Groups
+++ This bug was initially created as a clone of Bug #250942 +++ When rebuilding the TM Helios SR2 contribution with basebuilder r36x_v20110209 in order to address bug 337045, there was a single change to the Mapfile: the org.eclipse.dstore.core bundle was updated and released with a new qualifier from CVS. As a result, its including feature (org.eclipse.dstore feature) got a new qualifier. The org.eclipse.dstore feature is included in the org.eclipse.rse feature, so I would have expected the qualifier of that feature to be updated to -- but it was not! This behavior may be problematic, since only the org.eclipse.rse feature is contributed to the Helios aggregator, so the aggregator won't see a change and might not adopt the new TM Build. I had never seen such lack of updating the qualifier with the basebuilder we previously use (R36_RC4). For investigation, zipped repos are available: - The new build with the r36x_v20110209 basebuilder: http://download.eclipse.org/tm/downloads/drops/M20110212-1700/tm-repo-M20110212-1700.zip - The previous build with the R36_RC4 basebuilder: http://download.eclipse.org/tm/downloads/drops/M-3.2.2RC2-201102011000/tm-repo-3.2.2RC2.zip
Could this be bug 208143? We often have to tag our features for the change to percolate up to top level feature when only incrementing the version of one bundle.
Yes, quite clearly this is a dup, thanks for the reference. I had searched for "feature qualifier" before filing this but missed that bug since its summary just has "qualifier". *** This bug has been marked as a duplicate of bug 208143 ***
