It would be great to deploy our java-mwapi jar file artifact to a central repo, like Maven Central or jcenter.
This would make our builds less dependent on tool labs.
This could also help getting the F-droid builds working again.
I think Maven Central would be preferred but might be a lot harder to do than jcenter.
Info for Maven Central: https://maven.apache.org/guides/mini/guide-central-repository-upload.html
| Subject | Repo | Branch | Lines /- | |
|---|---|---|---|---|
| Add fallback json Gradle project | apps/android/wikipedia | master | 41 -5 | |
| Replace Maven build system with Gradle | apps/android/java-mwapi | master | 334 -88 |
@yuvipanda We don't have experience with this yet but maybe you would provide some guidance and also provide some info about https://repo1.maven.org/maven2/org/mediawiki/api/1.3/api-1.3.pom, something you uploaded to Maven Central 2 years ago. (Is this related to java-mwapi?)
Some background on why you chose to create your own repo based on tool labs after you uploaded the aforementioned artifacts would be great, too.
Nice article on uploading to jCenter and Maven: http://inthecheesefactory.com/blog/how-to-upload-library-to-jcenter-maven-central-as-dependency/en
We need to make sure that we can also upload SNAPSHOT versions to OSSRH. Some interesting links:
https://oss.sonatype.org/#view-repositories;snapshots~browsestorage
http://www.sonatype.org/nexus/2015/06/02/how-to-publish-software-artifacts-to-maven-central/
https://docs.gradle.org/current/userguide/publishing_maven.html
http://central.sonatype.org/pages/gradle.html
Change 223718 had a related patch set uploaded (by Niedzielski):
Replace Maven build system with Gradle
Change 223720 had a related patch set uploaded (by Niedzielski):
Add fallback json Gradle project