From 12c975888a762f0f901391a1bf27703360d179d0 Mon Sep 17 00:00:00 2001
From: Jaikiran Pai <jaikiran@apache.org>
Date: Sat, 24 Mar 2018 11:20:02 +0530
Subject: [PATCH] Fix junitlauncher doc to be clear that the classpath element
 isn't used for looking test engines or junit launcher APIs

---
 manual/Tasks/junitlauncher.html | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/manual/Tasks/junitlauncher.html b/manual/Tasks/junitlauncher.html
index 75eb5b381..16bcee177 100644
--- a/manual/Tasks/junitlauncher.html
+++ b/manual/Tasks/junitlauncher.html
@@ -150,13 +150,10 @@
 </p>
 <ul>
     <li>Finding the test classes to execute</li>
-    <li>Finding the JUnit 5 framework libraries (which include the API jars and test engine
-        jars). The complete set of jars that are relevant in JUnit 5 framework are listed in
-        the <a href="#junit5deps">dependencies</a> section</li>
 </ul>
 <p>
     If the <code>classpath</code> element isn't configured for the task, then the classpath of Ant
-    itself will be used for finding the test classes and JUnit 5 libraries.
+    itself will be used for finding the test classes.
 </p>
 
 <h4>listener</h4>