From 7ce5c4e85a52e52a1d14619691f64a2819ee54bb Mon Sep 17 00:00:00 2001
From: Cedric Beust
- Since Kobalt's build files are actual Kotlin files, not only can you leverage auto-completion - to write your build files but the full power of your IDEA is at your fingertips to write - these files in any way you see fit: using expressions, conditionals, classes, extension functions, - constants... The sky is the limit! -
-- Kobalt uses Kotlin's type safe builder pattern to offer a DSL that's extremely similar to Gradle - and minimalistic while allowing you to switch to full Kotlin code whenever necessary. -
-- Here is an example of the auto-completion dialog: -
-
-
-
- And see the following section to get a feel for Kobalt's build file syntax. -
-For example, here is JCommander's entire build file: @@ -133,7 +112,31 @@ val jcommander = project {
This build file also includes a directive to upload your artifacts to Bintray automatically.
-+ Since Kobalt's build files are actual Kotlin files, not only can you leverage auto-completion + to write your build files but the full power of your IDEA is at your fingertips to write + these files in any way you see fit: using expressions, conditionals, classes, extension functions, + constants... The sky is the limit! +
++ Kobalt uses Kotlin's type safe builder pattern to offer a DSL that's extremely similar to Gradle + and minimalistic while allowing you to switch to full Kotlin code whenever necessary. +
++ Here is an example of the auto-completion dialog: +
+
+
+
+ And see the following section to get a feel for Kobalt's build file syntax. +
+ + +Most of Kobalt's core tasks are incremental, which means that if you run them without having changed anything, they will be skipped. The support for incremental tasks is also trivial to add for plug-in developers, which guarantees that your builds with Kobalt will always be as fast as they can be.