Update the manual of junitlauncher task as well as add a note in WHATSNEW about the changed class names of that task

WHATSNEW

@@ -8,6 +8,13 @@ Changes that could break older environments:
    supporting Java Advanced Imaging are removed; imageio task (based on
    ImageIO and AWT) is provided as a replacement.
 
+ * junitlauncher task has changed the class names and package names of
+   the task as well as some of the supporting classes of that task. If
+   any code depended on these class or package names, they will have to
+   be updated to reference these newly named classes. This however,
+   doesn't impact build scripts if their reference to junitlauncher task
+   was merely through the use of the <junitlauncher> element.
+
 Fixed bugs:
 -----------
 
@@ -46,8 +53,8 @@ Other changes:
  * the <modified> selector has a new built-in algorithm 'lastmodified'
    which computes a value based upon the lastmodified time of the file.
 
- * junitlauncher task now supports forking and can be used with JaCoCo
-   (see https://github.com/jacoco/jacoco/issues/673).
+ * junitlauncher task now supports running tests in a forked JVM. More
+   details available in the junitlauncher task manual.
 
  * signjar and verifyjar now support the -providerName, -providerClass
    and -providerArg command line options of keytool via new attributes.

manual/Tasks/junitlauncher.html

@@ -576,6 +576,24 @@ the new JVM instance that will be created to launch the tests.
             than this configured value, then the JVM is killed</td>
         <td>No</td>
     </tr>
+    <tr>
+        <td>includeJUnitPlatformLibraries</td>
+        <td>If set to <code>true</code>, then the jar files that make up the
+        JUnit platform, will be included in the runtime classpath of the forked
+        JVM. If set to <code>false</code>, then the <a href="#nested-classpath">configured classpath</a>
+        of this task, which will be made available to the runtime classpath of the forked
+        JVM, is expected to contain the JUnit platform library jars</td>
+        <td>No. Value defaults to <code>true</code>.</td>
+    </tr>
+    <tr>
+        <td>includeAntRuntimeLibraries</td>
+        <td>If set to <code>true</code>, then the jar files that make up the
+            Ant runtime, will be included in the runtime classpath of the forked
+            JVM. If set to <code>false</code>, then the <a href="#nested-classpath">configured classpath</a>
+            of this task, which will be made available to the runtime classpath of the forked
+            JVM, is expected to contain the Ant runtime jars</td>
+        <td>No. Value defaults to <code>true</code>.</td>
+    </tr>
 </table>
 
 The <code>fork</code> element allows the following nested elements: