~update comments

Author: qwwdfsad

integration-testing/build.gradle

@@ -22,6 +22,7 @@ dependencies {
 
 sourceSets {
     // Test that relies on Guava to reflectively check all Throwable subclasses in coroutines
+    // Also other non-specific tests piggyback on that one
     withGuavaTest {
         kotlin
         compileClasspath += sourceSets.test.runtimeClasspath

integration-testing/src/withGuavaTest/kotlin/Jdk8InCoreIntegration.kt

@@ -8,7 +8,7 @@ import org.junit.Test
 import kotlin.test.*
 
 /*
- * Temporary test that verifies both signatures from jdk8 and from core source-sets are used
+ * Integration test that ensures both signatures from jdk8 and from core source-sets are used
  */
 class Jdk8InCoreIntegration {
 

kotlinx-coroutines-core/build.gradle

@@ -44,9 +44,9 @@ The overall structure is just a hack to support the scenario we are interested i
 * We would like to have two source-sets "core" and "jdk8"
 * "jdk8" is allowed to use API from Java 8 and from "core"
 * "core" is prohibited to use any API from "jdk8"
-* It is okay to have test in a single test source-set
-* We want to validate source-sets with animal sniffer separately
+* It is okay to have tests in a single test source-set
 * And we want to publish a **single** artifact kotlinx-coroutines-core.jar that contains classes from both source-sets
+* Current limitation: only classes from "core" are checked with animal-sniffer
 
 For that, we have following compilations:
 * jvmMain compilation: [jvmCoreMain, jdk8Main]
@@ -145,7 +145,7 @@ kotlin {
 
         /* Create compilation for jvmCore to prove that jvmMain does not rely on jdk8 */
         compilations.create('CoreMain') {
-            /* jvmCore is automatically matched as 'defaultSourceSet' for the compilation */
+            /* jvmCore is automatically matched as 'defaultSourceSet' for the compilation, due to its name */
             tasks.getByName('check').dependsOn(compileKotlinTaskProvider)
         }
     }