ICU-2062 update readme, also see build.xml updates
X-SVN-Rev: 9567
This commit is contained in:
Doug Felt
parent
bf75d537d3
commit
59bcd6a463
@ -68,12 +68,12 @@ do not apply.</blockquote>
|
||||
</ul>
|
||||
In some cases, the above support has been rolled into a later release of
|
||||
Java. For example, the Thai word-break is now in Java 1.4. However, if you
|
||||
are using Java 1.2, you can use the ICU4J package until you upgrade to 1.4.
|
||||
are using Java 1.3, you can use the ICU4J package until you upgrade to 1.4.
|
||||
</p>
|
||||
|
||||
<h3><a name=license></a><u>License Information</u></h3>
|
||||
<p>
|
||||
The ICU projects (ICU4C and ICU4J) now use the X license. The X license is a non-viral and recommended free software license that is compatible with the GNU GPL license. This became effective with release 1.8.1 of ICU4C and release 1.3.1 of ICU4J in mid-2001. All new ICU releases will adopt the X license; previous ICU releases continue to utilize the IPL (IBM Public LIcense). Users of previous releases of ICU who want to adopt new ICU releases will need to accept the terms and conditions of the X license.
|
||||
The ICU projects (ICU4C and ICU4J) now use the X license. The X license is a non-viral and recommended free software license that is compatible with the GNU GPL license. This became effective with release 1.8.1 of ICU4C and release 1.3.1 of ICU4J in mid-2001. All new ICU releases will adopt the X license; previous ICU releases continue to utilize the IPL (IBM Public License). Users of previous releases of ICU who want to adopt new ICU releases will need to accept the terms and conditions of the X license.
|
||||
</p>
|
||||
<p>
|
||||
The main effect of the change is to provide GPL compatibility. The X license is listed as GPL compatible, see the gnu page at <a href=http://www.gnu.org/philosophy/license-list.html#GPLCompatibleLicenses>
|
||||
@ -94,9 +94,6 @@ compiled using a Java 1.2.x or 1.3.x compiler, as even components that run using
|
||||
language features that are only present in Java2. Currently 1.1.x is unsupported and
|
||||
untested, and you use the components on a 1.1.x system at your own risk.</p>
|
||||
|
||||
<p>ICU4J is currently not compatible with JDK1.4 (in beta as of this writing). We anticipate adding
|
||||
support for JDK1.4 in a future release.</p>
|
||||
|
||||
<h3><a NAME="obtaining"></a><u>How to Download ICU4J</u></h3>
|
||||
|
||||
<p>There are two ways to download the ICU4J releases.
|
||||
@ -132,8 +129,7 @@ support for JDK1.4 in a future release.</p>
|
||||
<li>WinCVS:<br>
|
||||
If you will be doing serious work on ICU4J, you should probably install a CVS client on
|
||||
your own machine so that you can do batch operations without going through the WebCVS
|
||||
interface. On Windows, we suggest the WinCVS client. The following is the example
|
||||
instruction on how to download ICU4J via WinCVS: <ol>
|
||||
interface. On Windows, we suggest the WinCVS client. To download ICU4J via WinCVS: <ol>
|
||||
<li>Install the WinCVS client, which you can download from the <a
|
||||
href="http://www.wincvs.org">http://www.wincvs.org</a>.</li>
|
||||
<li>Select <strong>Preferences</strong> from the <strong>Admin</strong> menu.<ol type="a">
|
||||
@ -197,10 +193,6 @@ drive and any directory on that drive that you chose to install icu4j into. </p>
|
||||
<td>build.xml</td>
|
||||
<td>Ant build file. See <a href="#HowToInstallJavac">How to Install and Build</a> for more information</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>buildall.bat</td>
|
||||
<td>A bat file for building ICU4J with Javac (not recommended)</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<p><b>The source directories mirror the package structure of the code. They contain source code and data files:</b> </p>
|
||||
@ -321,7 +313,7 @@ We strongly recommend using the Ant build system to build ICU4J:</p>
|
||||
<li>It's recommended to install both the JDK and Ant somewhere <em>outside</em> the ICU4J
|
||||
directory. For example, on Linux you might install these
|
||||
in /usr/local.</li>
|
||||
<li>Install a recent JDK, version 1.2.x or 1.3.x will work. ICU4J does not yet build with JDK 1.4.</li>
|
||||
<li>Install a recent JDK, version 1.3.x or 1.4.x will work.</li>
|
||||
<li><p>Next install the <a href="http://jakarta.apache.org/ant/"><strong>Ant</strong></a> build
|
||||
system, part of the Apache Software Foundation's <a href="http://jakarta.apache.org/"><strong>Jakarta</strong></a>
|
||||
project. Ant is a portable, Java-based build system similar to make. ICU4J uses Ant
|
||||
@ -394,24 +386,32 @@ targets, see the build.xml file:</p>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>zip</td>
|
||||
<td>Create a zip archive of the source, docs, and jar file for distribution, excluding
|
||||
unwanted things like CVS directories and emacs backup files. The zip file <strong>icu4jYYYYMMDD.zip</strong>
|
||||
<td>Create a zip archive of the source, docs, and jar file for distribution. The zip file <strong>icu4jYYYYMMDD.zip</strong>
|
||||
will be created in the directory <em>above</em> the root ICU4J directory, where YYYYMMDD
|
||||
is today's date. Any existing file of that name will be overwritten.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>richeditZip</td>
|
||||
<td>Create a zip archive of the richedit docs and the richedit jar file (which contains only the
|
||||
classes needed by richedit) for distribution, excluding
|
||||
unwanted things like CVS directories and emacs backup files. The zip file <strong>richedit.zip</strong>
|
||||
will be created in the <strong>./richeditDist</strong> subdirectory. Any existing file of
|
||||
that name will be overwritten.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>zipsrc</td>
|
||||
<td>Like the <strong>zip</strong> target, without the docs and the jar file. The zip file <strong>icu4jsrcYYYYMMDD.zip</strong>
|
||||
will be created in the directory <em>above</em> the root ICU4J directory.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>richedit</td>
|
||||
<td>Build the richedit core class files and tests.
|
||||
</tr>
|
||||
<tr>
|
||||
<td>richeditJar</td>
|
||||
<td>Create the richedit jar file (which contains only the richedit core class files).
|
||||
The file <strong>richedit.jar</strong>
|
||||
will be created in the <strong>./richedit</strong> subdirectory. Any existing file of
|
||||
that name will be overwritten.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>richeditZip</td>
|
||||
<td>Create a zip archive of the richedit docs and jar file for distribution. The zip file <strong>richedit.zip</strong>
|
||||
will be created in the <strong>./richedit</strong> subdirectory. Any existing file of
|
||||
that name will be overwritten.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>clean</td>
|
||||
<td>Remove all built targets, leaving the source.</td>
|
||||
@ -439,9 +439,15 @@ exception of richedit) are <strong>unsupported</strong> and may change
|
||||
or disappear without notice.</p>
|
||||
<p>The icu4j.jar file contains only the core ICU4J classes, not the
|
||||
demo classes, so unless you build ICU4J there is little to try out.
|
||||
But you can try out the <strong>richedit</strong> package, since a GUI
|
||||
is included in the core. To run it, type:
|
||||
<tt><blockquote> java -classpath icu4j.jar com.ibm.richtext.demo.EditDemo [-swing][file]</blockquote></tt>
|
||||
|
||||
To try out the <strong>richedit</strong> package, first build the richeditJar target.
|
||||
This is a 'runnable' jar file. To run the richedit demo, type:
|
||||
<tt><blockquote> java -jar richedit/richedit.jar</blockquote></tt>
|
||||
|
||||
This will present an empty edit pane with an awt interface.</p>
|
||||
|
||||
<p>With a fuller command line you can try out other options, for example:
|
||||
<tt><blockquote> java -classpath richedit/richedit.jar com.ibm.richtext.demo.EditDemo [-swing][file]</blockquote></tt>
|
||||
This will use an awt GUI, or a swing GUI if
|
||||
<tt>-swing</tt> is passed on the command line. It will open a text
|
||||
file if one is provided, otherwise it will open a blank page. Click
|
||||
|
||||
Loading…
Reference in New Issue
Block a user