Description Alex Blewitt 2011-06-22 07:04:09 EDT

The Indigo release (http://download.eclipse.org/releases/indigo/compositeContent.jar) contains the following child update sites:

<children size="4">
<child location="http://download.eclipse.org/technology/epp/packages/indigo/" /> 
<child location="201105200900" /> 
<child location="201105270900" /> 
<child location="201106030900" /> 
</children>

The EPP contains outdated content too (see bug 350032) but has the following children:

<children size="3">
<child location="http://download.eclipse.org/technology/epp/packages/indigo/RC3.181/" /> 
<child location="http://download.eclipse.org/technology/epp/packages/indigo/RC2.173/" /> 
<child location="http://download.eclipse.org/technology/epp/packages/indigo/RC1.162/" /> 
</children>

Either the inclusion of outdated EPP children or the multiple 20110520/0527/0603 sites cause outdated bundles to be made visible via P2, which both consumes additional space in the various content.jar files but also increases the load on the server (and its downstream mirrors), for example:

org.eclipse.epp.package.scout_1.4.0.20110519-0955.jar
org.eclipse.epp.package.scout_1.4.0.20110526-1025.jar
org.eclipse.epp.package.scout_1.4.0.20110526-1646.jar

These won't be visible to P2 update clients (if they have 'hide older versions' enabled) but serve no beneficial purpose. I suspect the EPP bug 350032 is to blame but am raising it here for visibility in case it's to do with the other child locations.