From 4a4edeb97f7ea7136f5da91bcfb56c4b7cfa4b79 Mon Sep 17 00:00:00 2001
From: Brian Clozel <bclozel@pivotal.io>
Date: Tue, 27 Aug 2019 22:26:25 +0200
Subject: [PATCH] Apply Artifactory Gradle plugin to build

Since gh-23282, our CI does not apply automatically the Artifactory
Gradle plugin during our build and we're now applying it "manually".
This commit backports this change since the build configuration is
shared between branches.

See gh-23282
---
 build.gradle                | 1 +
 gradle/publish-maven.gradle | 5 +++++
 2 files changed, 6 insertions(+)

diff --git a/build.gradle b/build.gradle
index 0a27d61094a..5e9a997798e 100644
--- a/build.gradle
+++ b/build.gradle
@@ -14,6 +14,7 @@ plugins {
 	id "org.jetbrains.kotlin.jvm" version "1.2.71" apply false
 	id "org.jetbrains.dokka" version "0.9.18"
 	id "org.asciidoctor.convert" version "1.5.8"
+	id "com.jfrog.artifactory" version '4.9.8' apply false
 }
 
 ext {
diff --git a/gradle/publish-maven.gradle b/gradle/publish-maven.gradle
index dad95c8452f..4813ce71d18 100644
--- a/gradle/publish-maven.gradle
+++ b/gradle/publish-maven.gradle
@@ -1,4 +1,5 @@
 apply plugin: "propdeps-maven"
+apply plugin: 'com.jfrog.artifactory'
 
 install {
 	repositories.mavenInstaller {
@@ -58,3 +59,7 @@ def customizePom(pom, gradleProject) {
 		}
 	}
 }
+
+artifactoryPublish {
+  publishConfigs('archives')
+}