Sets a property if a resource is available at run time. This resource can be a file, a directory, a class in the classpath, or a JVM system resource.
+Note: a class is available in the classpath when it can be loaded; i.e., all +classes it depends on must be in the classpath, too.
If the resource is present, the property value is set to true
by default; otherwise, the
property is not set. You can set the value to something other than the default by specifying
the value attribute.
<classpath> element to specify the location of the
- test engines. For more details about this approach, please read the
+ test engines. For more details about this approach, please read the
using classpath element to include test engines section.
@@ -171,22 +171,22 @@
The <classpath> can be used to include the test engines that you want to be
- considered for execution of the tests.
+ considered for execution of the tests.
- NOTE: An important aspect to remember is that
- whether or not you use this approach, the JUnit 5 platform libraries
- listed earlier in this
+
+ NOTE: An important aspect to remember is that
+ whether or not you use this approach, the JUnit 5 platform libraries
+ listed earlier in this
document and the
Below is an example of setting up the classpath to include the Jupiter test engine during the
- execution of the tests. We assume that the JUnit 5 platform libraries and the
+ execution of the tests. We assume that the JUnit 5 platform libraries and the
ant-junitlauncher.jar, shouldn't be part of this classpath
- and instead they must be included in Ant runtime's classpath either by placing them
+ and instead they must be included in Ant runtime's classpath either by placing them
in ANT_HOME/lib or by passing the -lib option.
ant-junitlauncher.jar have been setup as explained previously.
-
+
<project>
<property name="output.dir" value="${basedir}/build"/>
@@ -206,35 +206,35 @@
<javac srcdir="${src.test.dir}"
destdir="${build.classes.dir}">
<classpath refid="junit.engine.jupiter.classpath"/>
- </javac>
- </target>
+ </javac>
+ </target>
<target name="test" depends="compile-test">
<junitlauncher>
<classpath refid="junit.engine.jupiter.classpath"/>
<classpath>
<pathelement location="${build.classes.dir}"/>
- </classpath>
+ </classpath>
<testclasses outputdir="${output.dir}">
<fileset dir="${build.classes.dir}"/>
<listener type="legacy-brief" sendSysOut="true"/>
<listener type="legacy-xml" sendSysErr="true" sendSysOut="true"/>
-
+
</testclasses>
</junitlauncher>
- </target>
+ </target>
</project>
- In the example above, the src/lib/jupiter directory is expected to contain
- the Jupiter test engine related jars (which have been
+ In the example above, the src/lib/jupiter directory is expected to contain
+ the Jupiter test engine related jars (which have been
listed in an earlier section of this
document). In the test target we use the classpath nested element
to point to the junit.engine.jupiter.classpath containing those jars. In this
- test target we also use another classpath element to point to
- the location containing our test classes. If required, both these classpath can be combined
+ test target we also use another classpath element to point to
+ the location containing our test classes. If required, both these classpath can be combined
into one.
-