Why this proposal again?
Libraries that are in Maven Central cannot have dependencies on libraries in other repositories (like JitPack).
So if any library located in Maven Central wants to use java-multibase then it simply cannot.
So, I propose to publish library to the Maven Central.
I did such publishing myself some time ago and the process turns out to be simple.
Of course I want to support with that, I can create an action on GitHub with the deployment (just a few simple steps in the .yml file) and show how it works on my forked repo.
The publishing to maven central topic has happened several times before (https://github.com/multiformats/java-multibase/issues/7 https://github.com/multiformats/java-multibase/issues/6).
Why this proposal again? Libraries that are in Maven Central cannot have dependencies on libraries in other repositories (like JitPack). So if any library located in Maven Central wants to use
java-multibase
then it simply cannot.So, I propose to publish library to the Maven Central. I did such publishing myself some time ago and the process turns out to be simple. Of course I want to support with that, I can create an action on GitHub with the deployment (just a few simple steps in the .yml file) and show how it works on my forked repo.
What do you think?