This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
PATCH: java/test.html removal
- From: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- To: gcc-patches at gcc dot gnu dot org, "" <java-patches at gcc dot gnu dot org>
- Cc: Janis Johnson <janis187 at us dot ibm dot com>
- Date: Sat, 23 Nov 2002 01:30:14 +0100 (CET)
- Subject: PATCH: java/test.html removal
java/test.html has been obsoleted by Janis' recent updates to the
installation documentation.
Gerald
Index: style.mhtml
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/style.mhtml,v
retrieving revision 1.48
diff -u -3 -p -r1.48 style.mhtml
--- style.mhtml 11 Nov 2002 23:21:07 -0000 1.48
+++ style.mhtml 23 Nov 2002 00:25:27 -0000
@@ -127,7 +127,6 @@
<a href="faq.html">FAQ</a><br />
<a href="docs.html">Documentation</a><br />
<a href="build-snapshot.html">Build</a><br />
- <a href="test.html">Testing</a><br />
<a href="contrib.html">Contributing</a><br />
<a href="done.html">Done with Gcj</a><br />
</p>
2002-11-23 Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
* test.html: Remove this file; its contents has been merged into the
installations instructions.
Index: java/test.html
===================================================================
RCS file: java/test.html
diff -N java/test.html
--- java/test.html 31 Oct 2002 14:47:43 -0000 1.9
+++ /dev/null 1 Jan 1970 00:00:00 -0000
@@ -1,67 +0,0 @@
-<html>
-<head>
-<title>GCJ - Testing</title>
-</head>
-<body>
-
-<h1>Testing GCJ</h1>
-
-<table border="0" cellpadding="4" width="95%">
-<tr bgcolor="#b0d0ff">
- <th align="left">
- General Runtime Tests
- </th>
-</tr>
-</table>
-<br />
-
-<p>Runtime tests are executed via <tt>'make check'</tt> from the <tt>testsuite</tt>
-directory of the libjava hierarchy in the build tree. Additional
-<a href="contrib.html#Testing">runtime tests</a> can be checked into the tree.
-Regression tests of the core packages in libgcj are run automatically via the
-<a href="#Mauve">Mauve test suite (described below)</a> if it is made available
-when the tests are being run.</p>
-
-<table border="0" cellpadding="4" width="95%">
-<tr bgcolor="#b0d0ff">
- <th align="left">
- <a name="Mauve">Mauve</a>
- </th>
-</tr>
-</table>
-<br />
-
-<p>The <a href="http://sources.redhat.com/mauve/";>Mauve Project</a> is a
-project to write a suite of tests for the Java Class Libraries. We
-encourage developers to contribute test cases to Mauve.</p>
-
-<p>libgcj supports Mauve testing. If you have Mauve checked out in,
-e.g., <tt>~/mauve/</tt>, then you can tell the libgcj to run the Mauve
-tests like so: <tt>make MAUVEDIR=~/mauve check</tt>.</p>
-
-<p>To highlight regressions, a mechanism has been set up in <tt>mauve.exp</tt>
-to track expected failures by comparing against the contents of
-<tt>libjava/testsuite/libjava.mauve/xfails</tt> from the source hierarchy.
-This file should be updated as new (failing) tests are added to Mauve or when
-fixes are made to libgcj that correct for failing Mauve tests.</p>
-
-<table border="0" cellpadding="4" width="95%">
-<tr bgcolor="#b0d0ff">
- <th align="left">
- Jacks
- </th>
-</tr>
-</table>
-<br />
-
-<p>The <a
-href="http://oss.software.ibm.com/developerworks/opensource/jacks/";>Jacks</a>
-project exists to create a test suite for Java compilers. We
-encourage developers to contribute test cases to Jacks.</p>
-
-<p>Changes affecting the gcj front end can usefully be tested against
-Jacks. We don't as yet have an automated mechanism to run Jacks tests
-in our test framework.</p>
-
-</body>
-</html>