On 10/20/2011 01:59 PM, Terry Parker wrote:
I just discovered this mailing list and the eclipse.org-rsync.sh
script, but I'm not sure if the standard Eclipse mirroring can be
used meet our needs. Ideally we would only mirror the most recent
release (e.g., 3.7.1 without 3.7.0). At the top level we use
composite repositories to tie together offerings from Eclipse, our
internally generated plug-ins, and other third party plugins, so
only getting an exact release works well. Does anyone have
suggestions on the best way for us to grab the 3.7.1 and future
releases? Is that the "releases" part of the mirror?
[apologies in advance if my reply shows up multiple times ... this
is my third attempt to send the message, using my correct email id.]
I would stick with the b3 aggregator approach ... but, I'm biased :)
(Since I use it to produce the common repo). Using it, you'd have a
full-fledge internal mirror that would be used by your internal
requests. That is, some of the p2 metadata is "converted" to be its
own self contained repository. If you use rsync, you end up with a
copy of some of (but not, easily, all) of the files you need, but
your users could still be directed back to "eclipse.org" to get some
of the (meta) data, even if ended up getting some of the "large"
artifacts (jars) from your internal mirror.
This rsync script (and this newsgroup list) is more for those
providing mirrors for _everyone_ to use. Some eclipse.org traffic,
for some artifacts, is diverted to these mirrors, but, as far as I
know, there's no provision for "internal mirrors" .... there could
easily be, the webmaster could answer some of that more
specifically, but, I do know for sure it would not produce an
"internal" p2 repository. I am sure with lots of tweaking you could
end up with that ... but, easier just to use the b2 aggregator to
start with, rather than using rsync and tweaks, IMHO.
The fact that you get "version conflicts" sounds like a bug,
somewhere ... perhaps in the way we use composite repos to combine
releases and service releases ... but ... could be many other
things. And, this list wouldn't be the place to discuss that ... you
could open a "cross project" bug, or discuss on b3 aggregator list.
HTH
|