Actually I'm proposing a predictable structure on 'central : g...@central.maven.org: maven2/<group-name-with-slashes-for-dots</<artifact-name>.git
(one minor fix versus previous description of the git:// location) Or for the three separate variant: g...@central.maven.org: maven2/<group-name-with-slashes-for-dots</<artifact-name>-classes.git g...@central.maven.org: maven2/<group-name-with-slashes-for-dots</<artifact-name>-javadocs.git g...@central.maven.org: maven2/<group-name-with-slashes-for-dots</<artifact-name>-sources.git More likely though (as you mentioned in your opening line) is the way homebrew works - you point at repos elsewhere, but control poms/shas etc on 'central. On Wed, May 17, 2017 at 3:59 PM, Manfred Moser <manf...@simpligility.com> wrote: > Having worked with repository managers and the implementation for various > formats on Nexus for years I think such a format is a bit like Bower. It is > a registry format that in turn points to git repositories that have the > content. > > From a corporate usage and implementation point of view this is a utter > nightmare since you would have to open up your systems to all those > different repositories and sites hosting them instead of just one. > > You also cant simply make a copy of the content or analyze it in the way > it manifests as binaries. > > I am not sure what you are looking for as benefits but from my point of > view this is maybe a fun experiment but not something that will ever take > off.. > > Manfred > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
