Re: [dash-dev] Maven repositories at Eclipse

[Alex Blewitt <alex.blewitt@xxxxxxxxx>]

On 20 Mar 2011, at 20:27, Aaron Digulla <digulla@xxxxxxxx> wrote:

Am 20.03.2011 15:13, schrieb Alex Blewitt

I have put {integration,milestone,nightly,release} as the defined set for the public repositories. I'm unsure what to do for orbit. If we include it in the public repositories, then it may prevent others from consuming from there and central. On the other hand, there may be some things in orbit which aren't available elsewhere that we need to address. I suspect we can fix this subsequently.

How about another virtual repo which includes public and orbit? That way, we can have both.

Makes some sense - what to call it though?

Lastly, this will be a little ugly as a URL:

http://maven.eclipse.org/nexus/content/groups/public

We may want to set up a rewrite rule

Agreed. But I'd map http://maven.eclipse.org/maven2/ to http://maven.eclipse.org/nexus/content/groups/ (i.e. one level above) so that all public groups appear under that URL.

/maven2/ is typically not a set of repos but rather a single (albeit virtual) repo. There's no reason we couldn't set up short names for others if desired e.g. /milestone -> /nexus/content/groups/milestone - but I wouldn't want to expose the set of them, not the least of which is that groups URL contains more than just Eclipse content. 

Alex