3 ms·
It's the file layout, for just one thing. You can't just point Maven (or many package managers) at a simple HTTP server without the correct layout. If you coul
by chrisseaton 7y ago
It's the file layout, for just one thing. You can't just point Maven (or many package managers) at a simple HTTP server without the correct layout.
If you could... they wouldn't have built this.
- danShumway 7y agoCan't you? http://repo.maven.apache.org/maven2/ http://repo.maven.apache.org/maven2/ looks a lot to me like a simple HTTP server. 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.
- chrisseaton 7y ago> ...without the correct layout 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.