@@ -175,7 +175,7 @@ | |||||
<p> | <p> | ||||
Below is an example of setting up the classpath to include the Jupiter test engine and | Below is an example of setting up the classpath to include the Jupiter test engine and | ||||
the JUnit platform libraries during the execution of the tests. | the JUnit platform libraries during the execution of the tests. | ||||
<br/> | |||||
</p> | |||||
<pre> | <pre> | ||||
<project> | <project> | ||||
@@ -228,8 +228,9 @@ | |||||
</target> | </target> | ||||
</project> | </project> | ||||
</pre> | </pre> | ||||
<p> | |||||
In the example above, | In the example above, | ||||
</p> | |||||
<ul> | <ul> | ||||
<li>The <code>src/lib/jupiter</code> directory is expected to contain | <li>The <code>src/lib/jupiter</code> directory is expected to contain | ||||
the Jupiter test engine related jars (which have been | the Jupiter test engine related jars (which have been | ||||
@@ -240,6 +241,7 @@ | |||||
<a href="#junit-platform-libraries">listed in an earlier section of this | <a href="#junit-platform-libraries">listed in an earlier section of this | ||||
document</a>)</li> | document</a>)</li> | ||||
</ul> | </ul> | ||||
<p> | |||||
In the <code>test</code> target we use the <code>classpath</code> nested element | In the <code>test</code> target we use the <code>classpath</code> nested element | ||||
to point to the <code>junit.engine.jupiter.classpath</code> and <code>junit.platform.libs.classpath</code> | to point to the <code>junit.engine.jupiter.classpath</code> and <code>junit.platform.libs.classpath</code> | ||||
containing those jars. | containing those jars. | ||||
@@ -602,13 +604,13 @@ The <code>fork</code> element allows the following nested elements: | |||||
<p> | <p> | ||||
Additional JVM arguments may be passed to the forked JVM via the <code>jvmarg</code> elements. | Additional JVM arguments may be passed to the forked JVM via the <code>jvmarg</code> elements. | ||||
For example: | For example: | ||||
</p> | |||||
<pre> | <pre> | ||||
<fork ...> | <fork ...> | ||||
<jvmarg value="-Djava.compiler=NONE"/> | <jvmarg value="-Djava.compiler=NONE"/> | ||||
... | ... | ||||
</fork> | </fork> | ||||
</pre> | </pre> | ||||
</p> | |||||
<p> | <p> | ||||
<code>jvmarg</code> allows all attributes described in <a href="../using.html#arg">Command-line Arguments</a> | <code>jvmarg</code> allows all attributes described in <a href="../using.html#arg">Command-line Arguments</a> | ||||
@@ -617,13 +619,13 @@ The <code>fork</code> element allows the following nested elements: | |||||
<h5>sysproperty</h5> | <h5>sysproperty</h5> | ||||
<p> | <p> | ||||
The <code>sysproperty</code> elements allow passing Java system properties to the forked JVM: | The <code>sysproperty</code> elements allow passing Java system properties to the forked JVM: | ||||
</p> | |||||
<pre> | <pre> | ||||
<fork> | <fork> | ||||
<sysproperty key="greeting" value="hello world"/> | <sysproperty key="greeting" value="hello world"/> | ||||
... | ... | ||||
</fork> | </fork> | ||||
</pre> | </pre> | ||||
</p> | |||||
<p> | <p> | ||||
The attributes for this element are the same as for <a href="../Tasks/exec.html#env">environment variables</a> | The attributes for this element are the same as for <a href="../Tasks/exec.html#env">environment variables</a> | ||||
</p> | </p> | ||||
@@ -279,7 +279,7 @@ which executes a particular module's main class. Attributes:</p> | |||||
<h4 id="nested-locale">locale</h4> | <h4 id="nested-locale">locale</h4> | ||||
<p>Specifies locales to include in linked image. May be specified multiple | <p>Specifies locales to include in linked image. May be specified multiple | ||||
times. Requires <code>jdk.localedata</code> module. Attributes: | |||||
times. Requires <code>jdk.localedata</code> module. Attributes:</p> | |||||
<table class="attr"> | <table class="attr"> | ||||
<tr> | <tr> | ||||
<th scope="col">Attribute</th> | <th scope="col">Attribute</th> | ||||
@@ -318,7 +318,7 @@ times. Attributes:</p> | |||||
<p>If the <code>resourceOrder</code> attribute is also present on the task, its | <p>If the <code>resourceOrder</code> attribute is also present on the task, its | ||||
patterns are treated as if they occur before patterns in nested | patterns are treated as if they occur before patterns in nested | ||||
<code><resourceOrder></code> elements.</p> | |||||
<code><resourceOrder></code> elements.</p> | |||||
<h4 id="nested-excludeResources">excludeResources</h4> | <h4 id="nested-excludeResources">excludeResources</h4> | ||||
<p>Excludes files from linked image tree. May be specified multiple times. | <p>Excludes files from linked image tree. May be specified multiple times. | ||||
@@ -423,7 +423,7 @@ patterns are treated as if they occur before patterns in nested | |||||
<h4 id="nested-releaseInfo">releaseInfo</h4> | <h4 id="nested-releaseInfo">releaseInfo</h4> | ||||
<p>Replaces, augments, or trims the image's release info properties. | <p>Replaces, augments, or trims the image's release info properties. | ||||
Can be specified multiple times. Attributes: | |||||
Can be specified multiple times. Attributes:</p> | |||||
<table class="attr"> | <table class="attr"> | ||||
<tr> | <tr> | ||||
<th scope="col">Attribute</th> | <th scope="col">Attribute</th> | ||||
@@ -575,7 +575,6 @@ jmod describe "$FOREIGN_JDK_HOME"/jmods/java.base.jmod | grep '^platform' | |||||
</pre> | </pre> | ||||
</li> | </li> | ||||
</ul> | </ul> | ||||
<ul> | |||||
</body> | </body> | ||||
</html> | </html> |