At Eclipse, Milestones don't stay around forever. We could deploy them
to a release, but in general they aren't long term artifacts at eclipse.
The tools like FindBugs, CheckStyle, Tycho itself, JavaDoc, and standard
plugins are used by the builds themselves. Plus there are going to be
coming some specific Maven plugins for eclispe related items. (i.e
signing etc).
And the settings.xml for the hudson user will need to have the mirror
statement set to pull from the maven.eclipse.org repo instead.
On 03/11/2011 12:51 PM, Alex Blewitt wrote:
On 11 Mar 2011, at 17:47, David Carver wrote:
Anybody eclispe project deploying a Milestone or Nightly build,
should deploy with -SNAPSHOT. You can easily control how many
SNAPSHOTS are kept around.
You mean Integration or Nightly, right? Milestones we'd probably want
to keep around as non-SNAPSHOT builds.
Also, the first thing I would like to see is just getting the
settings.xml file setup and start setting up the Proxy's for the
repos that the various Projects use. This way we can help cut down
on the amount of download time there is for fetching artifacts.
I think it is good to come up with standards for group ids, etc, but
the simpliest thing to get going first is the Proxying of the repos
we need.
Do we know what maven builds have dependencies? All the Tycho stuff
will resolve with P2. Also, isn't the point of 'orbit' to be the
list-of-things that are needed outside of the Eclipse cloud, rather
than anything on central? I'm all for having an orbit repository
within the maven.eclipse.org <http://maven.eclipse.org> repository but
we should consider whether we need to proxy anything else.
Alex
_______________________________________________
dash-dev mailing list
dash-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/dash-dev