Is Artifactory immutable? Or I guess that it handles versioning/publishing better?
[0]: https://help.github.com/en/articles/linking-to-releases
[0] https://chiselapp.com/user/rkeene/repository/hashcache/ [1] http://hashcache.rkeene.org/
SHAs can't be changed, but they can be deleted. And on GitHub, entire projects, usernames, orgs can be deleted. Or renamed. In case of a user rename, GitHub does maintain redirects for awhile. Until that username is taken by somebody else.
So yea, does not seem to be a problem that actually exists.
Surely you must be joking.
Yes it is a big concern and the solution is to use repositories that aren't so volatile.
Fortunately a copyright takedown request is not a typical scenario, but it does happen, even with "immutable" repositories like maven-central.
In other words a "copyright takedown request" isn't valid, unless the author was in violation of the copyright of somebody else while publishing those packages and this was decided in a court of law.
It might happen, but I have never heard of Maven Central packages being removed.
But I do see GitHub repos being renamed or removed all the time and I have seen NPM packages removed, for no reason other than the author wanted so, screwing the entire JavaScript ecosystem.
The DMCA process is law. Maven Central (like anyone else who hosts things) have to respond to valid takedown requests (which means taking down content long before any court case; even if a counter-notice is filed the content still has to be taken down temporarily) or else they'd become liable for infringement themselves. It's less common than on github or NPM, sure (which I suspect has more to do with the complexity of maven central's registration process than anything else), but it happens and any host on the scale of maven central needs a process in place for doing it.
Granted this is quite the esoteric edge case... at least for now. ;-)
Before this new service how would you use GitHub as a source for installing, for example, Maven packages?
Does Maven do something more complicated like automatically figure out which platform binary to pull?
If you could... they wouldn't have built this.
I'll take your word on it though. I don't know much about how Java package management works, and like you said, I assume the Github team wouldn't waste their time building something that wasn't necessary.
I guess if nothing else it would be a pain in the neck to have to know in advance how release files had to be laid out.
How are you going to recreate that directory structure with GitHub releases? You can't even have any custom directories - they're just release-name/file-name.
I mean just try recreating it yourself and see how far you get.
You could try use GitHub pages instead, but GitHub very actively pester you if it even looks like you're distributing binaries there.
http://www.lordofthejars.com/2011/09/questa-di-marinella-e-l...
I am... really confused by this.
Isn't this just Github? Github is a hosting service that allows you to host your packages and code in one place. It has testing and publishing pipeline support, you can add artifacts/releases, make your packages private or public, host different types of software at the same time, and it's compatible with most existing dependency systems, including NodeJS.
I can see this has more download statistics, which is nice. And it has a policy that artifacts can't be deleted, which is very nice.
Is that it though? I know I have to be missing something; what can I do now that I couldn't already do with Github as is?