|
| Re: Prevent p2 materializer from contacting other sites [message #385518 is a reply to message #385517] |
Thu, 28 May 2009 05:46  |
 Achim Demelt
Messages: 160
Registered: July 2009 |
Senior Member |
|
|
Hi,
a good night's sleep and some more digging in the p2 documentation revealed
the following:
1) Setting the system property eclipse.p2.mirrors to false will completely
prevent any automatic mirror selection.
2) Providing a policy.xml file on our mirror update site gives more fine-
grained control over mirror selection.
See http://wiki.eclipse.org/Using_Policy_Files
Sorry for the noise.
Achim
Achim Demelt wrote:
> Hi,
>
> We have a local mirror of the Ganymede update site behind our firewall.
> The mirror is built using p2's site mirroring capabilities. I use the
> eclipse.import reader with an http://... URL. Unfortunately, file:/...
> access is not possible, but still, intranet http access should be an
> improvement over http access to ecipse.org.
>
> I then used the p2 materializer to fetch some features from this mirror.
> My first attempts led to Buckminster hanging indefinitely (both headless
> and regular IDE installation). After a while I found out that it tried to
> download something from www.eclipse.org. I must assume that this is due to
> the p2 materializer, because the old targetPlatform materializer worked
> fine.
>
> Setting a proxy solved my problem, of course. But I wonder if there is a
> way to prevent the p2 materializer from contacting other sites? This is
> not only for performance reasons. If external sources are taken into
> account, can I really be sure that Buckminster fetches only the things
> provided on our local mirror?
>
> Cheers,
> Achim
|
|
|
Powered by
FUDForum. Page generated in 0.03126 seconds
] 
Search
Help
Register
Login
Home
