Distributing to a public or private maven repository (en)
summary
Compares concrete publishing paths and the real effort required: JitPack builds any GitHub repo as Maven artifacts and works immediately with git tags or commits; Bintray gives web UI and easy uploads and is recommended if Android Studio search discoverability matters; Nexus requires GPG signing and Jira registration and takes days to enable; Artifactory offers a private repo plus caching for internal builds; using Wagon Git needs custom existence check to avoid overwrites and the author supplies a script to prevent accidental reuploads.
AI-written summary · about
chapters (16)
- 0:00Start
- 2:53identifies artifacts
- 7:01start uploading
- 7:43sign your artifacts
- 8:04upload an artifact
- 12:51add the dependencies on the build script
- 14:38add jetpack as a maven repository
- 16:54declare a dependency on your own host
- 19:30configure the plug-in
- 20:18configure the artifactory plugin
- 21:27consume the artifacts
- 23:30store the artifacts
- 23:59apply the maven plugin
- 24:35define a custom configuration
- 27:04add the maven dependency
- 27:51configuring a git repository internally in your company
related talks
18mAutomated Distribution of Open Source and Private Components with JFrog Bintray
40mWhat I Learned from Publishing Libraries to Maven Central
44mBuilding and Publishing Android Libraries the Missing Guide
16mReleasing at the speed of light
25mReleasing at the speed of light
25mReleasing Fast, Easy and Consistently
10m#DevOpsSpeakeasy
31mBuilding a private CI/CD pipeline with Java and Docker in the Cloud