In order to have Jitpack correctly recognize the artifacts, the requirements for an android library are a little bit different from those of a normal java library. So I didn't draw inspiration from NewPipeExtractor, but rather from another android library published on Jitpack (MPAndroidChart). Now the build succeeds and the correct artifacts are collected (if I remove the com.github.dcendents.android-maven plugin, as I would do in a java-only library, the artifact collection fails).
This PR removes the coralibre-sdk/ subfolder and moves all of its contents to the repository root. Other java libraries are usually structured this way (see NewPipeExtractor for example), and this allows jitpack to be used without problems. The two resulting .gitignores were merged.
In order to have Jitpack correctly recognize the artifacts, the requirements for an android library are a little bit different from those of a normal java library. So I didn't draw inspiration from NewPipeExtractor, but rather from another android library published on Jitpack (MPAndroidChart). Now the build succeeds and the correct artifacts are collected (if I remove the
com.github.dcendents.android-maven
plugin, as I would do in a java-only library, the artifact collection fails).This PR removes the
coralibre-sdk/
subfolder and moves all of its contents to the repository root. Other java libraries are usually structured this way (see NewPipeExtractor for example), and this allows jitpack to be used without problems. The two resulting.gitignore
s were merged.Fixes #36