| commit | dbe3f48f8854a7bd72019ba296acd5d676257caa | [log] [tgz] |
|---|---|---|
| author | Vsevolod Tolstopyatov <qwwdfsad@gmail.com> | Wed Apr 17 17:51:13 2019 +0300 |
| committer | Vsevolod Tolstopyatov <qwwdfsad@gmail.com> | Wed Apr 17 17:51:13 2019 +0300 |
| tree | 81bd356c69fbfef1e2259908c039849daefd5245 | |
| parent | 43983505033a67719b0621572b868fc55f492016 [diff] |
Fix test masks for snapshot builds
Library support for Kotlin coroutines with multiplatform support. This is a companion version for Kotlin 1.3.30 release.
GlobalScope.launch { delay(1000) println("Hello from Kotlin Coroutines!") }
launch and async coroutine builders;Job and Deferred light-weight future with cancellation support;MainScope for Android and UI applications.Dispatchers object with Main dispatcher for Android/Swing/JavaFx, and Default dispatcher for background coroutines;delay and yield top-level suspending functions;Channel and Mutex communication and synchronization primitives;coroutineScope and supervisorScope scope builders;SupervisorJob and CoroutineExceptionHandler for supervision of coroutines hierarchies;select expression support and more.Dispatchers.IO dispatcher for blocking coroutines;Executor.asCoroutineDispatcher() extension, custom thread pools, and more.Promise;Window.Dispatchers.setMain to override Dispatchers.Main in tests.DebugProbes API to probe, keep track of, print and dump active coroutines.CoroutinesTimeout test rule to automatically dump coroutines on test timeout.CompletableFuture, Guava ListenableFuture, and Google Play Services Task;MDCContext.The libraries are published to kotlinx bintray repository, linked to JCenter and pushed to Maven Central.
Add dependencies (you can also add other modules that you need):
<dependency> <groupId>org.jetbrains.kotlinx</groupId> <artifactId>kotlinx-coroutines-core</artifactId> <version>1.2.0</version> </dependency>
And make sure that you use the latest Kotlin version:
<properties> <kotlin.version>1.3.30</kotlin.version> </properties>
Add dependencies (you can also add other modules that you need):
dependencies { implementation 'org.jetbrains.kotlinx:kotlinx-coroutines-core:1.2.0' }
And make sure that you use the latest Kotlin version:
buildscript { ext.kotlin_version = '1.3.30' }
Make sure that you have either jcenter() or mavenCentral() in the list of repositories:
repository {
jcenter()
}
Add dependencies (you can also add other modules that you need):
dependencies { implementation("org.jetbrains.kotlinx:kotlinx-coroutines-core:1.2.0") }
And make sure that you use the latest Kotlin version:
plugins { kotlin("jvm") version "1.3.30" }
Make sure that you have either jcenter() or mavenCentral() in the list of repositories.
Core modules of kotlinx.coroutines are also available for Kotlin/JS and Kotlin/Native. If you write a common code that should get compiled for different platforms, add org.jetbrains.kotlinx:kotlinx-coroutines-core-common:<version> to your common code dependencies.
Add kotlinx-coroutines-android module as dependency when using kotlinx.coroutines on Android:
implementation 'org.jetbrains.kotlinx:kotlinx-coroutines-android:1.2.0'
This gives you access to Android Dispatchers.Main coroutine dispatcher and also makes sure that in case of crashed coroutine with unhandled exception this exception is logged before crashing Android application, similarly to the way uncaught exceptions in threads are handled by Android runtime.
For R8 no actions required, it will take obfuscation rules from the jar.
For Proguard you need to add options from coroutines.pro to your rules manually.
R8 is a replacement for ProGuard in Android ecosystem, it is enabled by default since Android gradle plugin 3.3.0-beta.
This library is built with Gradle. To build it, use ./gradlew build. You can import this project into IDEA, but you have to delegate build actions to Gradle (in Preferences -> Build, Execution, Deployment -> Build Tools -> Gradle -> Runner)
JAVA_HOME environment variable.JDK_16 environment variable. It is okay to have JDK_16 pointing to JAVA_HOME for external contributions.All development (both new features and bug fixes) is performed in develop branch. This way master sources always contain sources of the most recently released version. Please send PRs with bug fixes to develop branch. Fixes to documentation in markdown files are an exception to this rule. They are updated directly in master.
The develop branch is pushed to master during release.