diff --git a/_jbake-site-sources/content/tour.md b/_jbake-site-sources/content/tour.md index 218517bd..7ec0a727 100644 --- a/_jbake-site-sources/content/tour.md +++ b/_jbake-site-sources/content/tour.md @@ -164,7 +164,8 @@ From a java project having a build definition as above (or just fully convention #### Basic tasks - `jerkar help` : outputs on console available methods and option for Jerkar in the current project -- `jerkar doDefault publish` : cleans, compiles, unit tests and produces artifacts (that was actually do the `JkJavaBuild#doDefault`method) then `publish` produced artifacts on a remote repository. +- `jerkar` : cleans, compiles, unit tests and produces artifacts (that is what actually does the `JkJavaBuild#doDefault` method) +- `jerkar doDefault publish` : same then `publish` produced artifacts on a remote repository. - `jerkar -fatJar=true -forkTests=true` : same but also produces a fat-jar (jar file containg all the runtime dependencies) and runs unit tests in a forked process. - `jerkar -fatJar -forkTests` : same, when field values are not mentioned, Jerkar uses a default value (true for boolean fields) diff --git a/tour.html b/tour.html index 6735bc1e..1e7978bc 100644 --- a/tour.html +++ b/tour.html @@ -182,7 +182,8 @@

What can you do now ?

From a java project having a build definition as above (or just fully conventional), you can perform many tasks :

Basic tasks

The last will result in the following artifact creation :
Created artifacts

Pluggin tasks

Template classes (JkBuild and JkJavaBuild) enable plugability by providing hooks on several methods.
A plugin is just a class extending JkBuildPlugin or JkJavaBuildPlugin and overriding default hook methods. Plugins can also provide their own methods.