diff --git a/WHATSNEW b/WHATSNEW
index 0088e067d..725a1a9c5 100644
--- a/WHATSNEW
+++ b/WHATSNEW
@@ -75,6 +75,13 @@ Other changes:
 
 * Data types like <path> can now be defined inside of <target>s
 
+* you can now specify a classpath for <style> - the XSLZ processor
+  will be loaded from this path
+
+* added a force attribute to <style> to support dependencies that the
+  task cannot determine itself (dependency on parameters, not file
+  modification times for example)
+
 Fixed bugs:
 -----------
 
@@ -124,7 +131,8 @@ Fixed bugs:
 * Allow DTD locations to be specified when building generic ejb-jars
 
 * Handle classpaths with spaces
-  
+
+* Make sure XSLT processors close their output files in <style>.  
 
 Changes from Ant 1.2 to Ant 1.3
 ===========================================
diff --git a/docs/manual/CoreTasks/style.html b/docs/manual/CoreTasks/style.html
index 464d8ab90..606913097 100644
--- a/docs/manual/CoreTasks/style.html
+++ b/docs/manual/CoreTasks/style.html
@@ -62,6 +62,24 @@ inclusion/exclusion of files works, and how to write patterns.</p>
     </td>
     <td align="center" valign="top">Yes</td>
   </tr>
+  <tr>
+    <td valign="top">classpath</td> 
+    <td valign="top">the classpath to use when looking up the XSLT
+      processor.</td>
+    <td align="center" valign="top">No</td>
+  </tr>
+  <tr>
+    <td valign="top">classpathref</td>
+    <td valign="top">the classpath to use, given as <a
+      href="../using.html#references">reference</a> to a path defined elsewhere.</td>
+    <td align="center" valign="top">No</td>
+  </tr>
+  <tr>
+    <td valign="top">force</td>
+    <td valign="top">Recreate target files, even if they are newer
+      than their corresponding source files or the stylesheet.</td>
+    <td valign="top" align="center">No</td>
+  </tr>
   <tr>
     <td valign="top">processor</td>
     <td valign="top">name of the XSLT processor to use.  Permissible values are
@@ -116,6 +134,10 @@ inclusion/exclusion of files works, and how to write patterns.</p>
   </tr>
 </table>
 <h3>Parameters specified as nested elements</h3>
+<h4>classpath</h4>
+<p>The classpath to load the processor from can be specified via a
+nested <code>&lt;classpath&gt;</code>, as well - that is, a 
+<a href="../using.html#path">path</a>-like structure.</p>
 <h4>param</h4>
 <p>Param is used to pass a parameter to the XSL stylesheet.</p>
 <h4>Parameters</h4>