And as I'm comfortable advocating for a few Git-centric alternates, GitHub could be a hosting platform for jars of classes too. I think I've established that it is efficient for storing binary classes.
The https://github.com/paul-hammant/mc-xs-classes/releases page on the mc-xs-classes I did for the blog entry, has downloads of tags. That's all the classes you'd want and the manifest in a a zip. The trouble is GitHub made a root directory which will break Java. So I raised a feature request - https://cloud.githubusercontent.com/assets/ 82182/26177670/9d0cc4b8-3b28-11e7-88e1-7e97f727623c.png Don't worry, I'm 0 for 10 or so. - Paul On Wed, May 17, 2017 at 5:37 PM, Paul Hammant <p...@hammant.org> wrote: > The Maven-using developer community cares that the dependency downloader > does its think that the uploader/deploy does too. Some new releases of > those, and some back releases for the hard breaks (if any) going back in > time - Maven1, Maven2 and whatever. > > Works well enough for Homebrew (https://github.com/homebrew - the core > repo is at 125MB). Sure there's been teething troubles, and Ruby was the > wrong choice for the DSL versus Python, but it is great really. > > > > On Wed, May 17, 2017 at 5:25 PM, Manfred Moser <manf...@simpligility.com> > wrote: > >> If you would run Central on git like that in a centralized manner you >> would have to find someone that does that hosting for you and you would >> have to get buy in from the community to use that - both extremely hard or >> impossible. >> >> And if you dont do that but instead go with the distributed system you >> end up with the registry model that I think just doesnt really work in the >> real world. >> >> manfred >> >> Paul Hammant wrote on 2017-05-17 13:39: >> >> > 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 >> >> >> >> >> > >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> >
