[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [p2-dev] Mirroring to proxy repositories
|
I have just added a bug for this:
Sorry it took so long.
Cheers,
Miles
Miles Daffin
Morgan Stanley | IDEAS PRACTICE
AREAS
20 Cabot
Square | Canary Wharf | Floor 01
London, E14 4QW
Phone: +44 20
7677-5119
Fax: +44 20 7056-4572
Miles.Daffin@xxxxxxxxxxxxxxxxx
I agree that being able to clear the
mirrorsURL property makes sense. Can you enter a bug for that?
The two situations where the update site
URLs in feature.xml are parsed are: - When contacting a legacy update site (site.xml, but no
metadata.xml) - When installing
bundles unzipped directly in eclipse/plugins or eclipse/dropins
If the feature.xml is being read in any
other case, it would be a bug. One possibility that comes to mind is that if
there is an I/O exception reading the metadata.xml it may fall back to reading
the site.xml file. The best way to ensure this isn't happening is to get rid of
your site.xml file if you still have one. This would mean your site won't be
compatibile with Eclipse 3.3 or earlier. There is more detail on how repositories get associated with an install
here: http://wiki.eclipse.org/Equinox/p2/Repository_Association
John
"Daffin, Miles \(IT\)"
<Miles.Daffin@xxxxxxxxxxxxxxxxx>
Sent by: p2-dev-bounces@xxxxxxxxxxx
11/28/2008 11:29 AM
|
Please respond
to
P2 developer discussions
<p2-dev@xxxxxxxxxxx> |
|
|
To
| "P2 developer discussions"
<p2-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| RE: [p2-dev] Mirroring to proxy
repositories |
|
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
From: p2-dev-bounces@xxxxxxxxxxx
[mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of John
Arthorne
Sent: 28 November 2008 16:16
To: P2 developer
discussions
Subject: Re: [p2-dev] Mirroring to proxy
repositories
I didn't think mirroring copied those references. If they do, please
open a bug.
Thanks,
John
"Baptiste MATHUS"
<ml@xxxxxxxxxx>
Sent by:
p2-dev-bounces@xxxxxxxxxxx
11/28/2008 10:32 AM
|
Please respond
to
P2 developer discussions
<p2-dev@xxxxxxxxxxx> |
|
|
To
| "P2 developer
discussions" <p2-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| Re: [p2-dev] Mirroring to proxy
repositories |
|
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='' 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
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.
