You want to mirror central so that we are limiting the outbound
bandwidth for the builds.
That is one of the big selling factors of Nexus to begin with, and as
more and more projects at eclipse start migrating to maven, the outbound
bandwidth will increase. Having the artifacts mirrored is key to
reducing the time it takes to download items.
I'm fine if we call the repos something else, but not mirroring external
repos that we need dependencies on is big concern to me.
Dave
On 03/19/2011 07:14 AM, Aaron Digulla wrote:
Am 19.03.2011 00:00, schrieb Alex Blewitt:
This would leave:
* Releases
* Maven central
* Central m1 shadow
Why mirror central? People should set up their own proxy. I'd vote that
our public Nexus server only serves Eclipse stuff.
If *we* need stuff, we should set up a second, internal Nexus server
which isn't visible to the public.
If the things we publish need something that is hard to find, either add
the necessary rules in the POM or put that in a "thirdparty" repo on
Nexus (so everything comes from a single source).
We might want to temporarily have a 'testing' repository so we can publish e.g.
the trial work that Aaron has been doing.
The testing repo should be permanent but things in there should be
purged after a while (say three-six months).
And as said in the other mails, we need repos for nightly, integration
and milestone builds.
The reason why I want to separate those:
1. I don't want to mix snapshots and releases
2. I don't want to keep milestones, and I builds forever.
3. This makes it easier to weed out old/broken stuff. If something has
happened, we can delete the whole N/I/M repo and rebuild it. If we mix
stuff from several sources, cleaning up a mess will be a lot more work.
4. It allows consumers to make sure they don't pollute their projects
with unwanted stuff by accident.
So please also add
* nightly
* integration
* milestones
Regards,
_______________________________________________
dash-dev mailing list
dash-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/dash-dev
