How to use local library snapshot?

[dpproduction]

I would like to use library from special branch, but I don't understand which files I should put to project...
I have compiled library, so there are many JARs like paparazzi-1.3.4-SNAPSHOT.jar, paparazzi-gradle-plugin-1.3.4-SNAPSHOT.jar, paparazzi-preview-processor-1.3.4-SNAPSHOT.jar.
Help me please which files needed for use Paparazzi locally ?

[TWiStErRob]

As far as I know: all of them.

I think your best bet is to:

• do a gradlew publishToMavenLocal
• adjust your repository listing to add mavenLocal(),
• so that you can use it as "normal",
• by just bumping the version number where necessary.

---

This is almost how the tests work in the repo:

paparazzi/build.gradle

Lines 70 to 75 in a2e9b03

	publishing {
	repositories {
	maven {
	name = "projectLocalMaven"
	url = rootProject.layout.buildDirectory.dir("localMaven")
	}

paparazzi/paparazzi-gradle-plugin/build.gradle

Line 51 in a2e9b03

dependsOn(':paparazzi:publishMavenPublicationToProjectLocalMavenRepository')

paparazzi/paparazzi-gradle-plugin/src/test/projects/test.settings.gradle

Lines 8 to 11 in a2e9b03

	repositories {
	maven {
	url "file://${rootDir}/../../../../../build/localMaven"
	}

but Gradle tests are special, normally you can achieve this with just mavenLocal(). Use the above quoted code only if you're not fine with the default ~/.m2 location.

[dpproduction]

Thanks for the answer.
I have tried this way but faced with a problem:
I call publishToMavenLocal then copy repo folder to my location.
Part of my module screenshot-testing build script:

buildscript {
    repositories {
        mavenCentral()
        google()
        maven {
            url "file://${rootDir}/screenshot-testing/localMaven"
        }
    }
    dependencies {
        classpath 'app.cash.paparazzi:paparazzi-gradle-plugin:1.3.5-SNAPSHOT'
    }
}

Gradle sync writes - Failed to resolve: app.cash.paparazzi:paparazzi:1.3.5-SNAPSHOT
Seems like it tries to load library from remote but not from local repo...

[TWiStErRob]

It seems that the plugin was resolved, which makes sense because you have buildscript repository, add the same repository for standard dependency resolution too. Notice that the code block you show only has 3 repos, while the error shows 6-8.