-
-
Notifications
You must be signed in to change notification settings - Fork 735
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish to Maven Central repository #1171
Comments
Thanks for opening this issue!
|
@parse-community/android-sdk Any suggetions? |
I need to learn about the process, so that I can contribute with the publication process. (Publish to Maven Central repository #1171) as I'm experienced with JitPack at this time. |
You'd have to get the owner of |
@mtrezza I have reviewed the Maven Central Publication Process and found out a Libray that makes the whole process eaiser with just a Gradle Plugin. Article: https://www.waseefakhtar.com/android/publishing-your-first-android-library-to-mavencentral/ Take a look at this. Thanks. |
There are also docs how to publish that in GitHub Actions: Looks pretty simple. |
Publishing is the simple part for sure! Here I have a configuration that publishes when I make a tag in Git. The setup/access is the hard part 😜 |
You can publish any library for free on maven or jitpack if it is open source, as for private sdk's you may need enterprise account. As for how to publish sdk i think there are lots of scripts out there already also we can have Developer Page for reference. |
New Feature / Enhancement Checklist
Current Limitation
Google published their new Google Play SDK Index to help developers evaluate (potential) SDKs for their projects. Parse Android SDK is not listed there, as one hard requirement seems to be that the SDK is published to Maven Central.
We used to publish on Maven Central initially, but then stopped some years ago (for reasons currently unknown). The last releases there are from 2018.
Feature / Enhancement Description
Publishing releases to Maven Central, instead of Jitpack, or maybe in addition to Jitpack if there is a good reason.
Example Use Case
n/a
Alternatives / Workarounds
n/a
The text was updated successfully, but these errors were encountered: