From 3ac81190cb3a3bc4787917277f47aa34ab11518c Mon Sep 17 00:00:00 2001 From: Rick Busarow Date: Tue, 30 Apr 2024 14:41:33 -0500 Subject: [PATCH] configure publishing for the release variant The publishing plugin didn't have any publications set up. The `./gradlew publish` and `./gradlew publishToMavenLocal` tasks would execute and pass, but they were essentially no-ops. Now, they'll actually create artifacts. --- build.gradle.kts | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/build.gradle.kts b/build.gradle.kts index 7eb4a7a..aac1f2a 100644 --- a/build.gradle.kts +++ b/build.gradle.kts @@ -13,6 +13,7 @@ * See the License for the specific language governing permissions and * limitations under the License. */ +import com.vanniktech.maven.publish.AndroidSingleVariantLibrary import com.vanniktech.maven.publish.MavenPublishBaseExtension import com.vanniktech.maven.publish.SonatypeHost import kotlinx.validation.ApiValidationExtension @@ -58,7 +59,7 @@ extensions.configure { "compose-tests", "compose-unsupported-tests", "sample", - "sample-compose" + "sample-compose", ) } @@ -78,6 +79,10 @@ subprojects { publishToMavenCentral(SonatypeHost.S01) signAllPublications() pomFromGradleProperties() + + configure( + AndroidSingleVariantLibrary(variant = "release", sourcesJar = true, publishJavadocJar = true), + ) } }