diff --git a/documentation/index.html b/documentation/index.html index b6b0ac1..bc5cb88 100644 --- a/documentation/index.html +++ b/documentation/index.html @@ -278,11 +278,11 @@ Available templates Plug-in: Kobalt "java" Generate a simple Java project "kotlin" Generate a simple Kotlin project - "kobalt-plugin" Generate a sample Kobalt plug-in project + "kobaltPlugin" Generate a sample Kobalt plug-in project
You can then invoke any of these templates with --init
:
-$ kobaltw --init kobalt-plugin +$ kobaltw --init kobaltPlugin Build this project with `./kobaltw assemble`
Kobalt just generated a full project that will create a simple Kobalt plug-in. This plug-in adds @@ -323,16 +323,17 @@ Available templates Plug-in: Kobalt "java" Generates a simple Java project "kotlin" Generates a simple Kotlin project - "kobalt-plugin" Generate a sample Kobalt plug-in project + "kobaltPlugin" Generate a sample Kobalt plug-in project Plug-in: Android - "android-java" Generate a simple Android Java project -
- We see the same plug-ins we just reviewed and a new one provided by the Android plug-in called
- "android-java"
. The --plugins
parameter expects a comma-separated list of plug-in
- id's and it acts as if you had specified these Maven id's in your Build.kt
file.
- The reason why this parameter is useful is that typically, when you run a template, you don't
- have a build file yet since you are starting a project from scratch.
-
+We see the same plug-ins we just reviewed and a new one provided by the Android plug-in called
+"android-java"
. The --plugins
parameter expects a comma-separated list of plug-in
+id's and it acts as if you had specified these Maven id's in your Build.kt
file.
+The reason why this parameter is useful is that typically, when you run a template, you don't
+have a build file yet since you are starting a project from scratch.
+