FYI: Final 0.09 documentation update

[Mark Wielaard]

Hi all,

This is the final patch for 0.09. It sets the version, adds the
important NEWS entries and updates the README to clearly mention some
active projects that are based on GNU Classpath but don't use it
directly that people might be interested in as discussed on the main
list.

2004-05-02  Mark Wielaard  <address@hidden>

       * configure.ac: Set version to 0.09.
       * README: Move text around. Add section on active projects which use
       modified versions of the libraries.
       * NEWS: Add important updates for this release.

Now building and testing the final version!

Cheers,

Mark

Index: configure.ac
===================================================================
RCS file: /cvsroot/classpath/classpath/configure.ac,v
retrieving revision 1.22
diff -u -r1.22 configure.ac
--- configure.ac        26 Apr 2004 21:31:04 -0000      1.22
+++ configure.ac        2 May 2004 13:39:24 -0000
@@ -6,7 +6,7 @@
 dnl define([AC_CACHE_LOAD], )dnl
 dnl define([AC_CACHE_SAVE], )dnl
 
-AC_INIT([GNU Classpath],[0.08+cvs],address@hidden,[classpath])
+AC_INIT([GNU Classpath],[0.09],address@hidden,[classpath])
 AC_CONFIG_SRCDIR(java/lang/System.java)
 
 AC_CANONICAL_TARGET
Index: README
===================================================================
RCS file: /cvsroot/classpath/classpath/README,v
retrieving revision 1.13
diff -u -r1.13 README
--- README      30 Apr 2004 12:32:15 -0000      1.13
+++ README      2 May 2004 13:39:24 -0000
@@ -1,4 +1,4 @@
-GNU Classpath README - Last updated: Arpil 30, 2004
+GNU Classpath README - Last updated: May 2, 2004
 
 GNU Classpath, Essential Libraries for Java is a project to create
 a complete "clean room" implementation of the Java class libraries 
@@ -7,6 +7,10 @@
 a number of free replacements for standard Java development tools like
 javadoc, javap, javah, and others.
 
+This is a development snapshot release only and is not ready for general
+purpose use.  You need to combine it at least with one of the development
+environments mentioned below.
+
 Eventually, these essential libraries for Java will work with as many 
 free JVMs as possible.  Complete development environments known to be
 based on GNU Classpath include (recommended for end users):
@@ -14,8 +18,8 @@
        * GCC with GCJ  (http://gcc.gnu.org/java/)
        * Kaffe         (http://www.kaffe.org/)
 
-Smaller (runtime only) environments based on GNU Classpath includei
-(recommended for GNU Classpath hackers):
+Smaller (runtime only) environments which work with unmodified GNU Classpath
+releases include (recommended for GNU Classpath hackers):
 
        * JamVM         (http://www.jamvmv.org/)
        * Jikes RVM     (http://www.ibm.com/developerworks/oss/jikesrvm/)
@@ -25,18 +29,22 @@
 with the latest GNU Classpath release (and in most cases directly with the
 development sources from CVS).
 
-See for other GNU Classpath based runtimes, compilers and tools the
-GNU Classpath website: http://www.gnu.org/software/classpath/stories.html
+Some tools come with their own customized version of GNU Classpath.
+Please check if there is a customised version available for the tool you
+use before trying the bare bones GNU Classpath release. We are working with
+the tool creators to keep the differences between the core classes as small
+as possible. Please tell us if you make GNU Classpath work with a new tool.
 
-This is a development snapshot release only and is not ready for general
-purpose use.  You need to combine it at least with one of the development
-environments mentioned above.
+Active projects which use modified versions of the Classpath libraries
+some of which synchronizes with the Classpath CVS head every couple of weeks:
 
-Most JVMs come with their own customized version of GNU Classpath.
-Please check if there is a customised version available for the JVM you
-use before trying the bare bones GNU Classpath release. We are working with
-the JVM creators to keep the differences between the core classes as small
-as possible. Please tell us if you make GNU Classpath work with a new JVM.
+       * IKVM.NET      (http://www.ikvm.net/)
+       * JC            (http://jcvm.sourceforge.net/)
+       * JNode         (http://jnode.sourceforge.net/)
+       * SableVM       (http://www.sablevm.org)
+
+See for a more complete list of GNU Classpath based projects the
+GNU Classpath website: http://www.gnu.org/software/classpath/stories.html
 
 See the file INSTALL for details on installing GNU Classpath.
 See the file NEWS for details on what is included in this release.
Index: NEWS
===================================================================
RCS file: /cvsroot/classpath/classpath/NEWS,v
retrieving revision 1.38
diff -u -r1.38 NEWS
--- NEWS        22 Apr 2004 16:18:36 -0000      1.38
+++ NEWS        2 May 2004 13:39:24 -0000
@@ -1,13 +1,62 @@
-New in release 0.09
+New in release 0.09 (2004/02/02)
+
+* Includes updated GNU JAXP version from 2004-02-01.
+* Native C code is now -ansi -pedantic (C89) clean and (almost) -Wall clean.
+* java.io is now implemented by delegating most tasks directly to java.nio.
+* Reworked/Optimized implementations of java.nio.Buffer and subclasses.
+* New javax.print, javax.print.attribute[.standard] and javax.print.event
+  packages and classes.
+* java.text attributed iterators support.
+* New javax.imageio, javax.imageio.event and javax.imageio.spi packages and
+  classes.
+* GNU Classpath can now load service providers that are described via
+  META-INF/services/* resources in extension JARs. This is useful for
+  implementing the various APIs that are supposed to be extensible via
+  custom plugins. For details, please see the documentation of
+  gnu.classpath.ServiceFactory.
+  Application developers are strongly discouraged from calling glibj
+  internal packages.  Instead, they might want invoke the newly implemented
+  javax.imageio.spi.ServiceRegistry.lookupProviders, which is a standard 
+  method for loading plug-ins.
+* New developers wanting to help the GNU Classpath project might want to
+  review the greatly expanded Hacker Guide included in the doc directory
+  or online at http://www.gnu.org/software/classpath/docs/hacking.html
+  Also the FAQ has been expanded. And when working from CVS you can now use
+  a simple autogen.sh script to get all autotools magic done automagically.
+* New configure option --with-glibj which defines how to install the glibj
+  class files as zip, as flat directory files or both (zip|flat|both)
+  [default=zip].  When working with multiple runtimes some of which might
+  not support bootstrap classes in zip files the --with-glibj=both option
+  is recommended (this does take extra disc space).
+* Two big code drops from the libgcj gui branch updating various java.awt
+  and javax.swing classes.
+* Multiple java.net.InetAdress fixes and java.rmi fixes.
+* ServerSocket.accept() now restarts listening when system call interrupted.
+* Much cleanups to make standard API doc valid XHTML (not completed yet).
+* A scan for unused variables and non-static invocation of static methods
+  turned up a couple of subtle bugs which have now all been fixed.
+* The Mauve testsuite has been cleaned up considerable and lots of issues
+  in the GNU Classpath core class implementation have been fixed.
 
 VM Interface changes:
 
 * java.lang.Class/VMClass interface was changed. The interface now no
-longer requires an instance of VMClass for each Class instance. Instead
-the field vmdata in Class is now of type Object.
+  longer requires an instance of VMClass for each Class instance. Instead
+  the field vmdata in Class is now of type Object.
 * GNU Classpath now assumes that JNI calls SetXField can modify final
-fields. This was previously used silently for System.in/out/err and should
-be considered as a feature now. 
+  fields. This was previously used silently for System.in/out/err and should
+  be considered as a feature now.
+* A new VMProcess and a sample JNI C implementation are now provided to
+  make Runtime.exec() work out of the box on some systems.  This requires
+  a small change to VMRuntime.exec() when a runtime wants to use it as the
+  default java.lang.Process implementation.
+* The implementation of most of java.io through java.nio moved serveral
+  runtime specific I/O methods. Most methods do have a generic default native
+  C JNI implementation in native/jni/java-nio.
+* Runtime support methods for java.io.File have been moved to VMFile which
+  also comes with a default JNI C implementation.
+* To support the new service provider mechanism runtimes must make sure that
+  extension JARs are made accessible via the default context class loader.
 
 New in release 0.08 (2004/12/03)

signature.asc
Description: This is a digitally signed message part