Note that compilation is done on

[rakibhasanbd4723]

JitPack servers, so buildscript must not use any non-portable configuration (like custom external tools). Additionally, users have to add JitPack repository to their buildscripts:

view rawbuild.gradle hosted with by GitHub
Note the repositories order. It matters when they contain artifact having the same coordinates but different content. Here you can read an article about that confusing dependency.

Wrap up
If high availability and ease for users are numero bulgarie essential to you, use Maven Central. Either directly or via sync from JCenter.

If your priority is to make your artifacts available quickly and you don’t want to spend much time on configuration, use JitPack – especially if they are used only by your other projects. You can always set up deployment to Maven Central later – for example after your library becomes more popular.

Good luck with your libraries’ distribution!

TweetLinkedInFacebook79Like1
Related posts
How to Provide Accessibility in Your Native Android App with Jetpack Compose | Part 2: Scaling • Text Size • Focus Order • Labeling
How to Provide Accessibility in your Android App | Part 3: Semantic Properties and Screen Orientation
How to Provide Accessibility in Your Native Android App with Jetpack Compose | Part 1