we are providing an update site that contains both site.xml and p2
artifacts stuff ( artifatcs.jar and contents.jar ), so our update site
can be cunsumed by any eclipse versions.
this is working well, but facing a little problem.
when trying to mirror this update site using p2.mirror and eclipse 3.6 ,
it seems the site.xml is fetched first and p2 recreates metadata from
it. as a results, i get some artifact.reference pointing to original
if i remove the site.xml, p2 gets correctly the metadata.
my question is : does p2 looks for a site.xml before doing anything ?
how do i tell p2.mirror not using site.xml in its miror process ?
Le 11/04/2012 15:03, Gonzague Reydet a écrit :
> Hey Stéphane,
> Did you find any solution for this issue?
> We are facing the same problem trying to install artifacts located on a
> mirrored repository that references the original location.