[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [tycho-user] Creating an aggregated p2 mirror with modified categories
|
Hi Tobias,
i've tried the following version scheme, but i get:
<feature url="" id="org.pex.feature" version="0.0.0">
Missing requirement: mirror 0.0.1 requires 'org.pex.feature.feature.group 0.0.0' but it could not be found
What should i use for the url attribute when specifying 0.0.0 as version?
regards
-robert
On Tue, Sep 25, 2012 at 1:45 PM, Oberlies, Tobias
<tobias.oberlies@xxxxxxx> wrote:
Use “0.0.0” as version in the category.xml
Regards
Tobias
Hi,
we're trying to create a repository mirror from a variety of 3rd party p2 repos. To create the mirrored repo, we're using the
tycho-p2-extras-plugin with the mirror goal. This works fine, however the generated repsitory will be categorized just like the mirrored features have
been categorized.
The features in the aggregated repo should be categorized differently though than the features in the originating repos. Currently
we're using a 2step build for this:
1. Create the mirrored repository using the tycho-p2-extras-plugin :
https://github.com/pdt-eg/p2-mirror/blob/master/org.pex.p2-mirror.aggregator/pom.xml
2. Create a new eclipse-repository using the (local) features from the previous build, but with a separate category.xml :
https://github.com/pdt-eg/p2-mirror/tree/master/org.pex.p2-mirror.mirror
The problem with this solution is, that the category.xml needs the hardcoded and specific versions of the features in the aggregated repo.
So anytime the version of one of the mirrored features changes, the category.xml needs to be updated manually.
Ideally, the process should be fully automated and run by a cronjob - where the latest features of the mirrored repos are categorized automatically.
Does anyone know if there's a way to do this?
regards
-robert
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user