Catherine
08/25/2023, 1:43 PMIaroslav Postovalov
08/28/2023, 2:45 PM./gradlew dist
) is more or less atomic. But you can publish only some artifacts of Kotlin to a repository (like only compiler, only Gradle plugin, etc.). But this will not significantly speed up the compilation, because Kotlin is compiled incrementally (only changed modules and their dependents are recompiled). Anyway, subsequent assemblies will be faster.
3. All Kotlin's tests should not be run locally, that's for sure. You can just run a certain test file related to your feature (please explain your changes then), or even single test methods (if you are debugging something, for example) in IntelliJ IDEA.Iaroslav Postovalov
08/28/2023, 2:58 PM./gradlew dist
gives you distributive of command-line compiler that is quite useful for trying your changes (in dist
directory).
2. ./gradlew assemble
just tries to build all modules (without running tests).
3. ./gradlew publishToMavenLocal
puts all Kotlin's artifacts to your local maven repository (usually, ~/.m2
)
4. ./gradlew publish
puts them to build/repo
directory
5. ./gradlew :kotlin-compiler-embeddable:publishToMavenLocal
updates only embeddable Kotlin Compiler's JAR
6. ./gradlew :kotlin-compiler-embeddable:assemble
only builds modules needed for embeddable Kotlin Compiler (without publishing or testing)
Particular test classes or methods are easier to be run just from IDEACatherine Moore
08/29/2023, 1:57 PM