Right, this is probably going to cause a bit more controversy than most patches...
Attached is a patch which begins an update of the GNU Classpath website. As many will have noticed, our pages have not worn well with age. The attached patch makes a number of changes to our initial page, making it better reflect Classpath in 2008 as opposed to Classpath circa. 2002 (at a guess). Notable points for discussion: * Change the discussion of releases to refer to 1.0 as a major release rather than a public release. Most of our 0.x releases have been pretty public! * Switch from using the kaffe.org JAPI results to builder's as these currently seem to be dead. Indeed, anyone clicking on them gets a really bad impression that we don't even implement 1.0... Unfortunately this means we only have 1.4 and 1.5 results. If someone could run JAPI against OpenJDK6 (e.g. those working on IcedTea), this would be much appreciated. I'd prefer not to link against the OpenJDK results as they represent an unstable API in the JDK itself (i.e. there are things we shouldn't fix as they are not yet finalised!) * I changed the Mauve results to point at builder as well. The previous page was nicer looking but antiquated. If someone wants to revive the older page instead, this would be welcomed. * Updated the roadmap and in the process open the discussion of a 1.0 release. I think we need to make a firm decision on this if GNU Classpath is to continue. A 1.0 release would actually be a good conclusion too, as people move towards OpenJDK (which seems to be the case). As you can see from the patch, I suggest we make 1.0 a release where the core (java.*) is at the 1.6 level. If you view the current comparisons with 1.5, you will see we are already further along the 1.6 path than might be thought, and I think we can achieve this subsection prior to a 1.7 JDK being made available. Other elements, like Swing, would be a bonus. More importantly, I suggest we aim to get several applications working well -- which these are I'll leave to discussion on here, but Eclipse, Tomcat and JBoss seem like good choices to me (given we've had efforts on all these already). Without making any guarantees this early, the end of the year would be a nice time to see this happen. Thoughts? -- Andrew :) Support Free Java! Contribute to GNU Classpath and the OpenJDK http://www.gnu.org/software/classpath http://openjdk.java.net PGP Key: 94EFD9D8 (http://subkeys.pgp.net) Fingerprint = F8EF F1EA 401E 2E60 15FA 7927 142C 2591 94EF D9D8
Index: doc/www.gnu.org/home.wml =================================================================== RCS file: /sources/classpath/classpath/doc/www.gnu.org/home.wml,v retrieving revision 1.47 diff -u -3 -p -u -r1.47 home.wml --- doc/www.gnu.org/home.wml 17 Sep 2005 12:37:27 -0000 1.47 +++ doc/www.gnu.org/home.wml 13 Mar 2008 21:57:27 -0000 @@ -1,6 +1,6 @@ #include "include/layout.wml" -<set-var last-modified-author="prk"> +<set-var last-modified-author="gnu_andrew"> <subject "GNU Classpath"> <box> @@ -20,11 +20,11 @@ create free core class libraries for use with virtual machines and compilers for the java programming language. </P> -<P>Classpath is still a work in progress. The first public release -will be version 1.0. There have been no public releases; however, pre-release -source code is available via GNU's anonymous <A href="https://savannah.gnu.org/cvs/?group=classpath";> -CVS server</A> , and snapshots of the Classpath tree have been released and -are available from <A href="ftp://ftp.gnu.org/gnu/classpath/";>ftp://ftp.gnu.org/gnu/classpath/</A> +<P>Classpath is still a work in progress. The first major release +will be version 1.0. Pre-release source code is available via GNU's anonymous +<A href="https://savannah.gnu.org/cvs/?group=classpath";> +CVS server</A> , and periodic snapshot releases of the Classpath tree are made +available on <A href="ftp://ftp.gnu.org/gnu/classpath/";>ftp://ftp.gnu.org/gnu/classpath/</A> </P> </boxitem> @@ -35,8 +35,8 @@ An up to date view of the current state obtained by looking at these resources. <ul> <li><createlink url="tasks.html" name="Task descriptions"></li> - <li>GNU Classpath vs: <createlink url="http://www.kaffe.org/~stuart/japi/htmlout/h-jdk10-classpath.html"; name="JDK 1.0"> <createlink url="http://www.kaffe.org/~stuart/japi/htmlout/h-jdk11-classpath.html"; name="JDK 1.1"> <createlink url="http://www.kaffe.org/~stuart/japi/htmlout/h-jdk12-classpath.html"; name="JDK 1.2"> <createlink url="http://www.kaffe.org/~stuart/japi/htmlout/h-jdk13-classpath.html"; name="JDK 1.3"> <createlink url="http://www.kaffe.org/~stuart/japi/htmlout/h-jdk14-classpath.html"; name="JDK 1.4"> (updated nightly)</li> - <li>GNU Classpath <createlink url="http://www.object-refinery.com/classpath/mauve/report/"; name="Mauve Results"></li> + <li>GNU Classpath vs: <createlink url="http://builder.classpath.org/japi/jdk14-classpath.html"; name="JDK 1.4"> <createlink url="http://builder.classpath.org/japi/jdk15-classpath.html"; name="JDK 1.5"> (updated ~3 times a day)</li> + <li>GNU Classpath <createlink url="http://builder.classpath.org/mauve/mauvereport.cgi"; name="Mauve Results"></li> </ul> </p> </boxitem> @@ -44,21 +44,28 @@ obtained by looking at these resources. <boxtitle><a name="roadmap">Classpath::Roadmap</a></boxtitle> <boxitem> <p> -GNU Classpath 1.0 will be fully compatible with the 1.1 and largely -compliant with the 1.2 API specification and will have a stable API -for interacting with virtual machines. +GNU Classpath 1.0 will be fully compatible with the 1.1 and 1.2 API +specifications, in addition to having significant (>95%) compatability +with the 1.3, 1.4, 1.5 and 1.6 APIs. Our target for this release will +be to be fully API compatabile with the core of 1.6 (i.e. java.*, not +javax.*) and to have a number of significant applications (to be determined +by user input) running well. The vast majority of the 1.4 and 1.5 APIs will +be available, along with a stable API for interacting with virtual machines. </p> <p> -Current snapshot releases have implementations for the following -packages (and some subpackages) <code>java.applet, java.awt, -java.beans, java.io, java.lang, java.math, java.net, java.rmi, -java.security, java.sql, java.text, java.util, java.util.jar, -java.util.zip, org.omg</code>. Not all classes and methods are implemented yet, -but most are. many of the implemented classes are already up to the -1.2 API spec. Some are already compliant with the 1.3 and 1.4 API -specification (there are preliminary implementations of -<code>java.nio</code> and <code>javax.swing</code>). +Current snapshot releases have implementations for most Java packages. The +live JAPI results above give further details on this. Major missing packages +with respect to 1.6 are in the javax.* namespace, including the web services +APIs (JAXWS). There is no current plan to implement these, given their +existing presence as a distinct element in +<createlink url="http://openjdk.java.net"; name="OpenJDK"/>. Thus, our preference +is to get this working with GNU Classpath rather than implement the entire API +from scratch. </p> +<p> +What we implement is largely based on user feedback. If there is a particular +API that is critical to your use of GNU Classpath, then please let us know. We +can then adjust our priorities accordingly. </boxitem>
signature.asc
Description: Digital signature
