doc/en/java/docs/howtoports.sgml
Nik Clayton dd365111ba Change every outstanding 'short' link to the FAQ or Handbook to use
the now mandatory 'long' format.  This should catch everything, with
the exception of the release notes.
2002-06-29 09:07:09 +00:00

34 lines
1 KiB
Text

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/java/docs/howtoports.sgml,v 1.4 2000/04/30 22:57:39 nik Exp $">
<!ENTITY title "FreeBSD Java Project: How To Make a Port">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
<html>
&header;
<table border="0">
<tr>
<td>
<P>General instructions can be found in the FreeBSD Handbook, under <A HREF="../doc/en_US.ISO8859-1/books/handbook/porting.html">Porting Applications</A>.
<P>For Java ports, there are unofficial standards:
<P><PRE>
1) If it's a library then jar files go into:
/usr/local/share/java/classes/
2) If it's a stand-alone application then jar files go into:
/usr/local/share/java/&lt;application-name&gt;/
and scripts to run it go into:
/usr/local/bin/
3) Documentation goes into:
/usr/local/share/doc/java/&lt;application-name&gt;/
</PRE>
<P>The more ported applications we have, the better.
</td>
</tr>
</table>
&footer;
</BODY>
</HTML>