|Re: [p2-dev] Helios Features Mirror|
An alternative for you might be to use the b3 aggregator . That is the tool that was used when creating the Helios and Indigo aggregations and it can be used for this type of use-case as well. It can be downloaded from our update site  and executed either as a freestanding headless product, or within your IDE complete with graphical editor.
Since the aggregator performs a validation prior to mirroring there are two "flaws" in Helios that must be catered for. One is explained here:
and the other is that the feature org.eclipse.jwt.feature was renamed to org.eclipse.jwt.feature in a service pack release which in turn leads to conflicts since both are included when trying to resolve a "canonical" repository.
This b3.aggr file will successfully create a validated, "as small as possible" mirror of Helios for three common environments (win32.win32.x86, linux.gtk.x86, linux.gtk.x86_64). You can add other environments using the editor.
<?xml version="1.0" encoding="ASCII"?>
<aggregator:Aggregator xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:aggregator="http://www.eclipse.org/b3/2010/aggregator/1.0.0" description="Used to test stuff that causes errors when added to the main repo model." label="Test Repo" buildRoot="build-test" packedStrategy="VERIFY">
<configurations operatingSystem="linux" windowSystem="gtk"/>
<configurations operatingSystem="linux" windowSystem="gtk" architecture="x86_64"/>
<contributions label="Platform Repo">
<mapRules xsi:type="aggregator:ValidConfigurationsRule" description="Cater for bad filtering in the epp.package.linuxtools requirement for org.eclipse.epp.package.linuxtools.feature.feature.group" name="epp.package.linuxtools" validConfigurations="//@configurations.1 //@configurations.2"/>
<mapRules xsi:type="aggregator:ExclusionRule" description="Exclude feature that has been renamed and hence causes conflicts." name="org.eclipse.jwt.feature.group" versionRange="[0.7.0,0.8.0)"/>
On 2011-04-11 06:10, Pascal Rapicault wrote:
Since there was no satisfying solution, I've just released code to the mirroring app that will perform the same resolution than the one performed at install time. This will be available in the next I build (Tuesday morning)