Description Samuel Wu 2008-06-10 18:32:16 EDT

Created attachment 104404 [details]
zipped update site 

Build ID: Build id: I20080605-1300

Steps To Reproduce:
1. Download and unzipped the attached update site project
2. Install the feature Parent feature 
3. Parent feature contains the following URL
   <url>
      <update label="my update site"
url="http://tpftoolkit.torolab.ibm.com/tpftoolkit/updates34p2/"/>
   </url>
4. Child feature contains the following URL
   <url>
      <update label="my update site"
url="http://tpftoolkit.torolab.ibm.com/tpftoolkit/updates34/"/>
      <discovery label="updateSiteName"
url="http://download.eclipse.org/eclipse/updates/3.4"/>
      <discovery label="secondaryUpdateSiteName"
url="http://download.eclipse.org/releases/ganymede"/>
   </url>
5. Expected behavior: the update site URL in parent feature shows in the available software site and the ones of the child feature don't
6. Result: none of them shows
Both of them are found in the manage sites and you have to manually enable it to add it to the available sites

On the feature properties pages of these two features, it's defined to let the parent feature handle the update. It doesn't work in this case.


More information:
This request comes from the fact that a product may depend on specific version of the common component. The product may be broken if the common components are allowed to update themselves. The update to any of the common component has to go through the main product feature. 
There is no way to achieve this target in the current P2. I can't image how can a user go through the huge list of all the update site URLs and pick up the right one.