From 1618e552c136e25d86bf0708e0d760841c77c139 Mon Sep 17 00:00:00 2001 From: Błażej Kardyś Date: Tue, 5 Jan 2021 17:59:38 +0100 Subject: Versioning (#1654) * Adding versioning mechanism for multimodule * Versioning improvement * Refactor configuration, add ordering * Fix integration tests * Change packages, unignore test Co-authored-by: Marcin Aman --- .../kotlin/org/jetbrains/dokka/gradle/AndroidAutoConfigurationTest.kt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'runners') diff --git a/runners/gradle-plugin/src/test/kotlin/org/jetbrains/dokka/gradle/AndroidAutoConfigurationTest.kt b/runners/gradle-plugin/src/test/kotlin/org/jetbrains/dokka/gradle/AndroidAutoConfigurationTest.kt index 76215762..455a906b 100644 --- a/runners/gradle-plugin/src/test/kotlin/org/jetbrains/dokka/gradle/AndroidAutoConfigurationTest.kt +++ b/runners/gradle-plugin/src/test/kotlin/org/jetbrains/dokka/gradle/AndroidAutoConfigurationTest.kt @@ -69,11 +69,13 @@ class AndroidAutoConfigurationTest { dokkaTasks.flatMap { it.dokkaSourceSets }.forEach { sourceSet -> /* + There is no better way of checking for empty classpath at the moment (without resolving dependencies). We assume, that an empty classpath can be resolved We assume, that a non-empty classpath will not be able to resolve (no repositories defined) */ + assertFailsWith { sourceSet.classpath.files } } } -} +} \ No newline at end of file -- cgit