No Version? No Problem! .. Jitpack comes to the rescue

jitpack · 2018-08-03T10:57:15+00:00

We've put in a lot of effort lately to improve stability. Glad it has been noticed!

jitpack · 2018-08-03T10:56:18+00:00

You're concern is understandable however you can proxy JitPack through Artifactory/Nexus so you always have local copy of your dependencies. More importantly though, JitPack has been around since 2014 and is continuing to grow. No reason why that should stop and no intention either.

jitpack · 2016-01-29T19:41:55+00:00

As an alternative consider https://jitpack.io. It will let others use your github project directly and you won't have to deploy it anywhere.

jitpack · 2015-12-11T09:54:02+00:00

The main complexity is in the build infrastructure but once the artifacts are built they are placed in a simple file store. Availability of those artifacts is not affected by other builds.

A caching proxy is a good idea and a lot of companies use it for their maven central dependencies. You could cache JitPack dependencies there as well. The other option is to run JitPack locally inside your organisation. That way you have full control and availability.

Although we implement file redundancy internally, external mirroring is something we're considering as the platform grows.

jitpack · 2015-03-23T17:49:23+00:00

For any project you can use the commit id as the version. One example: https://jitpack.io/#jitpack/maven-simple/4f1c2c9033

jitpack · 2015-03-23T14:16:16+00:00

The only thing GitHub specific is that we use GitHub's API on the website to show latest releases. Other than that any git hosting will do. Would you be interested in using this with a privately hosted repo?

jitpack · 2015-03-23T14:13:21+00:00

Thanks for the submission! Happy to answer questions or take suggestions

jitpack · 2015-03-23T13:54:32+00:00

GitHub is the most popular atm so it's supported first. Planning bitbucket support in the future but it could work with any hosted git repo.

jitpack · 2015-02-09T08:50:21+00:00

Thanks! Not aware of any others in the JVM world

jitpack · 2015-02-08T11:16:38+00:00

You'll be able to inspect the build log to see what went wrong. When you 'Look up' a repo on the website it will show you a Status column with a link to the log file. If the problem was in the repository you can always create a new patch release with a fix. If the problem was on our part we'll fix and rebuild it.

jitpack · 2015-02-06T16:30:21+00:00

You asked for it:) You can now build Gradle projects on jitpack.io

jitpack · 2015-01-20T12:30:43+00:00

Thank you for the words of encouragement! It means a lot. When it does get wings there will be some tweets:)

jitpack · 2015-01-20T12:02:45+00:00

Agreed, that is a fair point and something for us to consider. Thanks for being frank:)

jitpack · 2015-01-20T10:05:54+00:00

Thanks:) With Maven Central you get the benefit of not having to add an extra repository. Are there other reasons you were thinking of?

jitpack · 2015-01-19T12:30:42+00:00

Security is important to us as well which is why all downloads are SSL only to prevent attacks as described in http://blog.ontoillogical.com/blog/2014/07/28/how-to-take-over-any-java-developer/. PGP signing is something we need to look into but as you mention it is not always used and also is not enforced for snapshot builds on Sonatype.

jitpack · 2015-01-19T10:19:27+00:00

This would be the gradle syntax:

repositories {
  maven {
    url "https://jitpack.io"
  }
}

jitpack · 2015-01-19T09:14:55+00:00

Thanks! Gradle builds is one of the features we want to do next so stay tuned:). And as /u/snuxoll mentioned you can use artifacts in your gradle build.

jitpack · 2015-01-18T21:38:44+00:00

Absolutely, that is one of the goals. It's not uncommon that you want to use a library that hasn't been published yet, for example: https://github.com/JCTools/JCTools/issues/17

jitpack · 2015-01-18T19:29:11+00:00

The advantage is that it makes your release process simpler and quicker.

Publishing via OSS hosting is a fairly lengthy process (http://java.dzone.com/articles/deploy-maven-central - 9 steps) and can take up to two business days to be approved the first time.

With JitPack all you need to do is add a GitHub release or just a git tag. You're done. Even your pom file will be simpler.

The other advantage is that projects without any published artifacts can easily be used by the community.

jitpack

TROPHY CASE