From b3a8d1a91c91379ef42f1ca0fe91566bed7e7bfc Mon Sep 17 00:00:00 2001
From: Cedric Beust <cedric@beust.com>
Date: Sat, 25 Jun 2016 09:18:53 -0700
Subject: [PATCH] Document buildFileClasspath().

---
 documentation/index.html | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/documentation/index.html b/documentation/index.html
index a88a412..2889f88 100644
--- a/documentation/index.html
+++ b/documentation/index.html
@@ -191,6 +191,19 @@ fun taskCreateVersion(project: Project) : TaskResult {
   This tasks takes a template file and replaces all occurrences of the string <code>"@version@"</code> with the actual version of the project. Obviously, this task is very specific to TestNG's own build and it wasn't worth writing a plug-in ftor this. Note the attributes <code>runBefore</code> and <code>runAfter</code>, which specify when this task will run. You can find more information about tasks in the <a href="http://beust.com/kobalt/plug-in-development/index.html#tasks">plug-in development section</a>.
 </p>
 
+<h3 class="section" indent="1" id="build-file-classpath">Build file classpath</h3>
+<p>
+  If you are writing code or an inline task in your build file that requires additional libraries,
+  you can specify these dependencies with the <code>buildFileClasspath()</code> directive, which accepts a list
+  of dependencies in parameters. Each of these dependencies will then be added to the classpath when
+  your build file is compiled and run:
+</p>
+<pre class="brush:java">
+// Build.kt
+val bfc = buildFileClasspath("org.testng:testng:6.9.11")
+val t = org.testng.TestNG()  // now legal
+</pre>
+
 <h3 class="section" indent="1" id="dependencies">Dependencies</h3>
 
 <p>