Community
Participate
Working Groups
+++ This bug was initially created as a clone of Bug #478337 +++ In the course of bug 478337 several short-cuts were made to accomplish the goal. This bug is to track improving the procedure to use API, and use the most efficient "p2 form". In no particular order: - p2 API should be used to create the composites, add new "children" and remove "old" children. - all metadata xml files should be *.jar files. - xz compressed versions should be provided for all metadata files (at least, in the 'simple' repositories. Not sure it matters for the tiny composites.
- The simple repositories should have "mirrorsurl" set.
Roland, Should this one be closed/fixed now?
I guess this bug could stay open. We're not using p2 API to create the composites for the same reason many other projects don't. It's still seems a bit overkill to set up an Eclipse instance to create a file that essentially looks like this : <?compositeMetadataRepository version='1.0.0'?> <repository name="..." type="org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository" version="1.0.0"> <properties size="1"> <property name="p2.timestamp" value="..."/> </properties> <children size="2"> <child location="..."/> <child location="..."/> </children> </repository> All metadata xml files are .jar files with the only exception being composite metadata repos. However I don't think these composites benefit from any significant size reduction (as is probably the motivation for shipping simple content xmls as jars). We also have xz compressed metadata files. We don't currently generate mirrorsurl for simple repositories but can probably implement this.
