Just-in-time packager for GitHub repositories
1–10 of 33 posts
Re: Just-in-time packager for GitHub repositories
#2It's an interesting concept. Instead of you uploading binaries the server builds and serves them. Any plans to support other build systems?
Re: Just-in-time packager for GitHub repositories
#3It's an interesting concept. Instead of you uploading binaries the server builds and serves them. Any plans to support other build systems?
There are! Probably Sbt first and then Leiningen.
Re: Just-in-time packager for GitHub repositories
#4Nice! This should make it a lot easier for developers to publish their projects.
Re: Just-in-time packager for GitHub repositories
#5Does jitpack currently support repositories in Github Enterprise?
Re: Just-in-time packager for GitHub repositories
#6Re: Just-in-time packager for GitHub repositories
#7Does jitpack currently support repositories in Github Enterprise?
Currently not. Actually you are the first to ask and it sounds like a great feature:) most likely that would mean you host jitpack on premises. It's something we don't provide yet but it is on the road map.
Re: Just-in-time packager for GitHub repositories
#8Love this project, almost surprising that nothing like this exists today for the maven world.
Re: Just-in-time packager for GitHub repositories
#9Nice! This should make it a lot easier for developers to publish their projects.
I thought the same. Publishing small JS libs is easy, just drop a Bower file and register it. For maven I need to build it, sign it, get access to a central repo (can take days) and then finally upload it.
Of course, this means that the quality is often much higher, but I think the barrier is a bit too high as it is right now.
Re: Just-in-time packager for GitHub repositories
#10Using source repositories as packages sounds like an awful idea. Not only do you have to deal with runtime dependencies, but also compile, test, and other dependencies. What happens if the tags are not numbers? What if a tag you are using is deleted?
Go ask the Erlang community about the issues they have with using GitHub repos as "packages". Here is a discussion about packaging: http://mostlyerlang.com/2015/01/27/054-packages/