|Re: [p2-dev] Mirroring to proxy repositories|
This is likely caused by reference URLs in your mirrored metadata repository. Look for a section like this in the content.xml/content.jar file:
<repository url="" href="http://download.eclipse.org/eclipse/updates/3.4" target="_blank">http://download.eclipse.org/eclipse/updates/3.4' type='0' options='0'/>
These references are added to the list of known repositories for the client when your repository is first loaded. Mirroring is controlled by a "p2.mirrorsURL" property in the artifact.xml file:
<property name='p2.mirrorsURL' value='http://www.eclipse.org/downloads/download.php?file=/eclipse/testUpdates&format=xml'/>
Removing this property will stop p2 from using mirrors for that repository.
There is more information on how repositories are managed, and descriptions of some open problems we are working on in this area here:
"Baptiste MATHUS" <ml@xxxxxxxxxx>
Sent by: p2-dev-bounces@xxxxxxxxxxx
11/22/2008 03:06 PM
Please respond to
P2 developer discussions <p2-dev@xxxxxxxxxxx>
To "P2 developer discussions" <p2-dev@xxxxxxxxxxx> cc Subject [p2-dev] Mirroring to proxy repositories
I seem to remember the subject was discussed somewhere, but can't find the thread back. At the moment, we use the mirrorApp to mirror something like 10 public repositories (that's why I noticed and logged the bug about non-working merging feature that was corrected in the 3.5M3).
The mirroring works fine (still not using the merging, though). But there's a problem : when I add the mirrored repository URL to my eclipse installation where I deleted all other repositories entries, I always end up having many repositories listed from the net.
The thing is: in the end, we wan't our developers to declare a unique Eclipse P2 repository that they'll use to update or install "supported" software... And at the moment, they could download it from the net directly and obtain a version we didn't test...
I guess those URL comes from the already installed plugins/features. So, how could we wipe them out, or ignore them or proxy them through our mirror every necessary time (and stop new mirrors from appearing automatically in the update interface...).
Is this something considered possible with P2? If so, could you please let me know how to do that?
Thanks a lot.
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !_______________________________________________
p2-dev mailing list
p2-dev mailing list