Am 20.03.2011 15:13, schrieb Alex Blewitt:
> I have put these repositories under /home/nexus/repositories with the
> nightly/milestone/integration as parent directories. This should allow
> us to roll forward with new releases as they come up, whilst
> aggregating under the repository URL for the group.
Very good. I like it.
> 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.
> 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 so that (e.g.)
>
> http://maven.eclipse.org/maven2/
> -> http://maven.eclipse.org/nexus/content/groups/public
>
> which would then let us use http://maven.eclipse.org/maven2 as the
> pubic facing URL for access to the outside world.
Agreed. But I'd map http://maven.eclipse.org/maven2/ to
http://maven.eclipse.org/nexus/content/groups/
<http://maven.eclipse.org/nexus/content/groups/public> (i.e. one level
above) so that all public groups appear under that URL.
Regards,
--
Aaron "Optimizer" Digulla a.k.a. Philmann Dark "It's not the universe
that's limited, it's our imagination. Follow me and I'll show you
something beyond the limits." http://blog.pdark.de/
_______________________________________________
dash-dev mailing list
dash-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/dash-dev
