Commit dbc530cd authored by Jamie Tanna's avatar Jamie Tanna

Blogument using the local Maven cache with Gradle

Closes #1013.
parent b997bd20
Pipeline #199445485 passed with stages
in 22 minutes and 26 seconds
title: "Publishing + Consuming Artefacts in the Local Maven Repository with Gradle"
description: "How to use Gradle to publish and consume artefacts build on your local machine."
- blogumentation
- java
- gradle
license_code: Apache-2.0
license_prose: CC-BY-NC-SA-4.0
date: 2020-10-07T20:51:06+0100
slug: "gradle-maven-local"
When you're working on shared libraries, it's quite likely that you'll want to test the new version of the library, before publishing it. This can generally be avoided if we have a snapshots repo, but still helps.
When using Gradle, we need to make sure that we have the `maven-publish` plugin added, which will then provide us the `publishToMavenLocal` task, which we can run as following:
./gradlew publishToMavenLocal
This then publishes to our local maven repository:
find ~/.m2/repository/me/jvt/hacking/library
Once the library is published, how can we consume it? We add the dependency [as with other dependencies]( but add `mavenLocal()`:
repositories {
+ mavenLocal()
I never check in these changes, because I've been burned by having this enabled on a project before. Maven pulls from the local Maven repository by default, so when I was running on a shared build platform, it led to inconsistent failing builds between my local machine and remotely as the version that's available may not be the version that's been tested and released. It similarly runs the risk that someone may have overwritten a version of the library that you're expecting to be correct, i.e. Apache commons.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment