Ok so you already know how to build your android library and publish it to JCenter/MavenCentral. This post is third in parts of a series.
If you come from the java world, you would already be knowing about MavenCentral in a big way. MavenCentral is the central repository which hosts all the maven artifacts and one can reference them from anywhere in the world.
Developers are a different kind of people altogether. They tend to be lazy but strive to be super efficient at the same time. A lot of this can be seen in the Android world where a certain library pops up everyday to solve a specific problem or to make the complex processes simpler.
I am pretty sure you would agree to the fact that the usual javadoc is not a something everyone likes. The colors are what makes it superrrrrrr boring.
If I were to ask a question to a room filled with android developers **“How many of you have been in that place of sheer helplessness and panic when your gradle build fails because of a version conflict in dependencies?
The world of artifacts and the way they make the life of a developer simpler, fascinates me to a great extent. For the same reason I have gone through a lot of good articles online, which explain how the whole process works.
Have you ever thought how the central repository works like Maven Central or JCenter? Is it possible to own one for yourself? Do you want to host your artifacts in your own private repository?
JACK & JILL are part of the new tool chain for android and in the words of Android Developer Blog they are designed to improve build times and simplify development by reducing dependencies on other tools