From 5cc23b2bfec6845dff21221096936508554a601e Mon Sep 17 00:00:00 2001
From: David Phillips <david@acz.org>
Date: Fri, 26 Jul 2019 14:26:56 -0700
Subject: [PATCH] Correctly publish artifacts on JitPack

The Gradle install target produces invalid POM files that are missing
the dependencyManagement section and versions for some dependencies.
Instead, we directly tell JitPack to run the correct Gradle target.
---
 build.gradle | 4 ----
 jitpack.yml  | 2 ++
 2 files changed, 2 insertions(+), 4 deletions(-)
 create mode 100644 jitpack.yml

diff --git a/build.gradle b/build.gradle
index fe08286d0494..282ce61d735f 100644
--- a/build.gradle
+++ b/build.gradle
@@ -64,10 +64,6 @@ subprojects {
   apply plugin: 'maven' // make pom files for deployment
   apply plugin: 'nebula.maven-base-publish'
 
-  artifacts {
-    archives sourceJar
-  }
-
   compileJava {
     options.encoding = "UTF-8"
   }
diff --git a/jitpack.yml b/jitpack.yml
new file mode 100644
index 000000000000..abeb8eecceb3
--- /dev/null
+++ b/jitpack.yml
@@ -0,0 +1,2 @@
+install:
+  - ./gradlew publishToMavenLocal