Upload libpebblecommon to jitpack #345
Comments
|
Agree that publishing somewhere else would be ideal! I mentioned in #337 I would be happy to help get it published to Maven Central and can put up a draft PR for what that might look like. Publishing to jitpack would definitely ease setup and unblock #337 but I tend to avoid jitpack as it's not really safe or secure |
|
I have a draft PR up (pebble-dev/libpebblecommon#31) and would need help from a maintainer to fully get publishing on Maven Central working. The docs have details on whats needed (The prerequisites all need to be done by a maintainer) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Personally, I find the setup progress for cobble way to complicated. Especially setting up a GitHub Token just to launch the app is cumbersome.
I think uploading libpebblecommon to jitpack would solve the issue, because we only need the GitHub Token to load the libpebblecommon package from GitHub. Jitpack does not have this restriction as far as I know.
Of course, jitpack is just meant for a "upload package somewhere else" service, I'm also open to other sites.
Another option would be to add libpebblecommon as a submodule and build it during app launch. However, I think this would break the purpose of having a seperate library.
The text was updated successfully, but these errors were encountered: