From 8d404fd02340b16ce9aa3470ddc707a0fa872752 Mon Sep 17 00:00:00 2001
From: Cedric Beust <cedric.beust@le.com>
Date: Wed, 5 Apr 2017 14:51:39 -0700
Subject: [PATCH] Additions for install{}.

---
 plug-ins/index.html | 25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)

diff --git a/plug-ins/index.html b/plug-ins/index.html
index c10cf3a..e3ca420 100644
--- a/plug-ins/index.html
+++ b/plug-ins/index.html
@@ -476,12 +476,37 @@ assemble {
 <p>
   The <code>install</code> section lets you specify how the artifacts get installed. If you don't specify any <code>install</code> directive, then the <code>install</code> task will install your artifacts in the <code>lib</code> directory by default.
 </p>
+<p>
+  The simplest configuration is to copy all the artifacts created to a directory:
+</p>
 <pre class="brush:java">
     install {
         libDir = "libs"
     }
 </pre>
 
+<p>
+  You can also be more selective in what you install with either the <code>copy</code> directive to copy
+  individual files or with <code>include</code>, which lets you specify more sophisticated ways of moving
+  files to a destination:
+</p>
+<pre class="brush:java">
+    install {
+        copy("README", to("deploy"))
+        include(from("kobaltBuild/libs"), to("deploy"), glob("**/*"))
+    }
+</pre>
+<p>
+  You might find the directive <code>collect()</code> useful when installing: this function is invoked on a
+  list of dependencies and returns a list of jar files that represent the transitive closure of the dependencies:
+</p>
+<pre class="brush:java">
+    install {
+        collect(compileDependencies).forEach {
+            copy(it.absolutePath, to("deploy"))
+        }
+    }
+</pre>
 <h2 class="section" id="publishing">Publishing</h2>
 
 <p>