[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
| Re: [p2-dev] Mirroring to proxy repositories | 
Yes, true, sorry. 
BTW, I just hit it again: after doing a full installation update, I had some public http repositories URL back. I guess they come from the updated features that were parsed after upgrading... 
IMO, that's quite unattended behaviour to have the mirrored URL back when you're actually trying to avoid directly hitting them :-).
Couldn't P2 be optionally set to never read/use the blocks like
<url>
    <update label="Maven Integration" url="" href="http://m2eclipse.sonatype.org/update/">http://m2eclipse.sonatype.org/update/"/>
  </url>
that it could find it the features?
Do you agree we could file an improvement request?
Cheers.
2008/11/28 Daffin, Miles (IT) 
<Miles.Daffin@xxxxxxxxxxxxxxxxx>
Mirroring does not copy the references but it does copy the 
mirrorsURL property. I think that this needs removing too to avoid 
potential 'contamination' of the P2 UI repo list with external 
sites.
 
Also it seems that external sites that are declared in 
feature.xml/url elements may somehow, under certain circumstances, be added to 
the P2 UI's list. However, I am still testing this and trying to get it 
reproducible.
 
HTH
 
Miles
I didn't think mirroring copied 
those references. If they do, please open a bug. Thanks, John 
I'm 
considering filing an enhancement request about having an option to have the 
mirroring application to wipe out those references to external sites (so that 
mirror users don't have those externals refs added automatically).
Is this 
something that could be acceptable?
Cheers.
2008/11/23 John Arthorne <John_Arthorne@xxxxxxxxxx> 
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: 
 <references size='6'> 
   <repository 
url="">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: 
http://wiki.eclipse.org/Equinox/p2/Repository_Association 
John 
Hi all,
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.
Cheers.
-- 
Baptiste <Batmat> MATHUS - 
http://batmat.net 
Sauvez un 
arbre,
Mangez un castor !_______________________________________________
p2-dev mailing 
list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev 
mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
-- 
Baptiste <Batmat> 
MATHUS - http://batmat.net
Sauvez un 
arbre,
Mangez un castor !_______________________________________________
p2-dev mailing 
list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
  
NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error.
  
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
-- 
Baptiste <Batmat> MATHUS - 
http://batmat.netSauvez un arbre,
Mangez un castor !