108 |
are instructions within the Mauve website on how to download and use Mauve. |
are instructions within the Mauve website on how to download and use Mauve. |
109 |
Writing Mauve tests is the most important thing GNU Classpath developers |
Writing Mauve tests is the most important thing GNU Classpath developers |
110 |
could do for the project at this time. |
could do for the project at this time. |
|
</en> |
|
111 |
</p> |
</p> |
112 |
|
<p> |
113 |
|
Java API compatibility testing can be performed using |
114 |
|
<link url="http://rainbow.netreach.net/~sballard/japi/" |
115 |
|
name="japitools">. Japitools already does |
116 |
|
full API comparisons but it doesn't have the capability to extract |
117 |
|
APIs from the documentation - instead, the "japize" tool uses the |
118 |
|
jode.bytecode library to identify the public members of a given set of |
119 |
|
packages from the binary jars or zips. But japitools does separate the |
120 |
|
API-inspection phase ("japize") from the compatibility-testing phase |
121 |
|
("japicompat") so it would be easy to offer an alternative to japize |
122 |
|
that worked on API documentation. |
123 |
|
</p> |
124 |
|
<p> |
125 |
|
Another method of API compatibility testing is to use <link |
126 |
|
url="http://majestix.ucnet.uoc.gr/~jgeorgal/pub/jdiff.sh" |
127 |
|
name="jdiff.sh">, at least until this functionality is merged into |
128 |
|
japitools. |
129 |
|
</en> |
130 |
|
|
131 |
<H4>Virtual Machines</H4> |
<H4>Virtual Machines</H4> |
132 |
<en> |
<en> |