nextcloud / nextcloud/android-library
Publish to a proper package repository
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 105
- Forks
- 99
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 21
Description
JitPack is highly convenient as it takes very little effort but it comes with some drawbacks:
- As its name implies, it only builds a version when somebody requests it. This means the first build with a new version either takes longer or just fails until it's built.
- Stability has not been the best as of late, with builds randomly failing because of JitPack server errors, and dependencies sometimes not being available.
- Additionally the web UI is clunky so it's fairly hard to debug what's wrong and to fix possible problems.
Moving forward, we should try to actively publish the library to a normal package repository. Obvious options are Maven Central and Github Package Registry.
This would of course require that we handle the build and push, but that can probably be accomplished in a simple way with Github Actions.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the current JitPack publishing setup and the repository's GitHub Actions configuration. Compare Maven Central and GitHub Packages requirements, then define a repeatable publishing workflow whose successful package release and failure handling can be verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, kotlin
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100