Re: GNU Classpath 0.08 released
Hi, On Sat, 2004-03-13 at 21:30, Etienne Gagnon wrote: It's so much easier with Subversion... ;-P You know: Subversion is now officially released (1.0.0)! Maybe it's time for Classpath to consider migrating? No kidding :) I did a 'cvs rtag -aR classpath-0_08-release classpath' which seems to have done the trick. So you get a 'clean' 0.08 release with 'cvs export -r classpath-0_08-release classpath' now. (But I recommend the release tar.gz file for normal devs since it also contains the generated auto* file, including a configure script.) Having subversion as a better CVS would be nice indeed. Hope Savannah will support it in the future. But I was actually hoping Graydon would tell us a bit more about his Monotone http://www.venge.net/monotone/ experiment. Of which he is the main author and which he was using to sync the gcj head and gui branches. Since we have multiple non-centralized development trees (classpath, gcc/libjava, sablevm-classpath, kaffe/libraries/javalib, etc) each with their own branches it seems a distributed version control system might be a real win for making collaborating easier. Cheers, Mark signature.asc Description: This is a digitally signed message part ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: GNU Classpath 0.08 released
Here is the complete list of resuscitated files: configure.in doc/www.gnu.org/docs/license.wml doc/www.gnu.org/docs/redistribution.wml gnu/java/awt/image/GdkPixbufDecoder.java gnu/java/awt/image/GtkOffScreenDecoder.java gnu/java/net/SocketInputStream.java gnu/java/net/SocketOutputStream.java gnu/java/net/protocol/file/FileURLConnection.java gnu/java/net/protocol/http/HttpURLConnection.java gnu/java/net/protocol/jar/JarURLConnection.java gnu/java/nio/GenericBuffer.cpp gnu/java/nio/GenericMappedByteFileBuffer.cpp java/nio/GenericBuffer.cpp javax/swing/ToggleButtonModel.java javax/swing/plaf/basic/BasicDefaults.java lib/gen_nio.sh.in native/jni/gtk-peer/gnu_java_awt_image_GdkPixbufDecoder.c vm/reference/java/lang/Runtime.java Etienne Etienne Gagnon wrote: Hi Mark, While importing Classpath into sablevm-classpath, using the classpath-0_08-release tag, I notice that you are resuscitating some files such as ./configure.in. Why isn't this file left into the Attic? Maybe it's just a tagging mistake. A good test, for a tag, is to do: cvs export -r tagname -d test classpath then compare: diff -r classpath test | sort | less So, maybe a thing to fix in 0.09? ;-) [It's considered bad practice (and it is painful in CVS) to change an existing tag. So, I recommend not changing the release-0_08-release tag.] Have fun! Etienne Mark Wielaard wrote: We are pleased to announce a new development release of GNU Classpath. ... -- Etienne M. Gagnon, Ph.D. http://www.info.uqam.ca/~egagnon/ SableVM: http://www.sablevm.org/ SableCC: http://www.sablecc.org/ ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: GNU Classpath 0.08 released
Hi, Etienne, On Sat, 2004-03-13 at 18:08, Etienne Gagnon wrote: While importing Classpath into sablevm-classpath, using the classpath-0_08-release tag, I notice that you are resuscitating some files such as ./configure.in. Why isn't this file left into the Attic? Maybe it's just a tagging mistake. A good test, for a tag, is to do: cvs export -r tagname -d test classpath then compare: diff -r classpath test | sort | less So, maybe a thing to fix in 0.09? ;-) [It's considered bad practice (and it is painful in CVS) to change an existing tag. So, I recommend not changing the release-0_08-release tag.] Drat. Sorry about that. Yes, I made a mistake while tagging. I had tested everything, up to and including a complete make distcheck and a mauve and vte test run on another clean machine, but then went back to my development machine for the final cvs tag. And of course did it in the wrong working directory... I had hoped that I had done the re-tagging correctly, but forgot about the old files. I should have send a warning to the list. Thanks for the list of files erroneously tagged. I looked at the cvs documentation and it seems that you can remove tags from Attic files using rtag -a but I am a bit afraid that might mess up the tagging even more. I promise to do better for 0.09. For now please check a cvs checkout against the official classpath-0.08.tar.gz file. Or does someone know the magic command to make it all right in the repository? Thanks, Mark signature.asc Description: This is a digitally signed message part ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: GNU Classpath 0.08 released
Hi Mark, While importing Classpath into sablevm-classpath, using the classpath-0_08-release tag, I notice that you are resuscitating some files such as ./configure.in. Why isn't this file left into the Attic? Maybe it's just a tagging mistake. A good test, for a tag, is to do: cvs export -r tagname -d test classpath then compare: diff -r classpath test | sort | less So, maybe a thing to fix in 0.09? ;-) [It's considered bad practice (and it is painful in CVS) to change an existing tag. So, I recommend not changing the release-0_08-release tag.] Have fun! Etienne Mark Wielaard wrote: We are pleased to announce a new development release of GNU Classpath. ... -- Etienne M. Gagnon, Ph.D. http://www.info.uqam.ca/~egagnon/ SableVM: http://www.sablevm.org/ SableCC: http://www.sablecc.org/ ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: GNU Classpath 0.08 released
On Sat, 2004-03-13 at 13:28, Mark Wielaard wrote: Hi, Etienne, On Sat, 2004-03-13 at 18:08, Etienne Gagnon wrote: While importing Classpath into sablevm-classpath, using the classpath-0_08-release tag, I notice that you are resuscitating some files such as ./configure.in. Why isn't this file left into the Attic? Maybe it's just a tagging mistake. A good test, for a tag, is to do: cvs export -r tagname -d test classpath then compare: diff -r classpath test | sort | less So, maybe a thing to fix in 0.09? ;-) [It's considered bad practice (and it is painful in CVS) to change an existing tag. So, I recommend not changing the release-0_08-release tag.] Drat. Sorry about that. Yes, I made a mistake while tagging. I had tested everything, up to and including a complete make distcheck and a mauve and vte test run on another clean machine, but then went back to my development machine for the final cvs tag. And of course did it in the wrong working directory... I had hoped that I had done the re-tagging correctly, but forgot about the old files. I should have send a warning to the list. Thanks for the list of files erroneously tagged. I looked at the cvs documentation and it seems that you can remove tags from Attic files using rtag -a but I am a bit afraid that might mess up the tagging even more. I promise to do better for 0.09. For now please check a cvs checkout against the official classpath-0.08.tar.gz file. Or does someone know the magic command to make it all right in the repository? Thanks, I would probably go ahead with the rtag -a. I think just make sure in the future to use rtag to avoid tagging local working directory files. Brian signature.asc Description: This is a digitally signed message part ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: GNU Classpath 0.08 released
Mark Wielaard wrote: Or does someone know the magic command to make it all right in the repository? cvs co classpath # no tags works fine, and does not export the dead files. In other words, the files *are* in the Attic; what you need to do is to get a clean working copy with no dead files so that next time you make a tag, no dead file gets tagged along the living files. It's so much easier with Subversion... ;-P You know: Subversion is now officially released (1.0.0)! Maybe it's time for Classpath to consider migrating? Etienne -- Etienne M. Gagnon, Ph.D. http://www.info.uqam.ca/~egagnon/ SableVM: http://www.sablevm.org/ SableCC: http://www.sablecc.org/ ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
GNU Classpath 0.08 released
We are pleased to announce a new development release of GNU Classpath. GNU Classpath, Essential Libraries for Java, is a project to create free core class libraries for use with virtual machines and compilers for the java programming language. GNU Classpath 0.08 can be downloaded from ftp://ftp.gnu.org/pub/gnu/classpath/ or one of the ftp.gnu.org mirrors http://www.gnu.org/order/ftp.html File: classpath-0.08.tar.gz MD5sum: 17f200744c31f36fdbe15347745562fb New in GNU Classpath 0.08: * java.util.regexp implementation through gnu.regexp wrappers. * java.net.URI implementation. * Working implementation of javax.swing.undo. * java.awt.geom.CubicCurve2D/QuadCurve2D: Can now solve cubic and quadratic equations; implementation adapted from the GNU Scientific Library. * Lots of java.awt and gtk+ peer improvements. Also more Swing work. Start of EmbeddedWindow support. * BufferedReader speed improvements. * Improved useabilty of java.text implementation for several applications. * ObjectInputStream is much faster and more compatible with other implementations. * Fix handling of alias methods, where a method has been deprecated in favour of a new one with the same funtion but a different name. (See Deprecated Methods section in the GNU Classpath Hacking Guide.) * javax.print.attribute.standard added. * Lots of java.nio, java.net, java.io fixes and updates. * Depend on autoconf 2.59+ and automake 1.7+, GCJ 3.3+, jikes 1.18+. VM Interface changes: * Split native methods in java.lang.Runtime into java.lang.VMRuntime. * Resources are now also loaded/needed through the bootstrap classloader (gnu.regexp needs MessageBundle included in glibj.zip Fixed Classpath bugs: #6095 java.awt.geom.QuadCurve2D.solveQuadratic sometimes gives wrong results #7099 EventListenerList.getListenerCount should accept null argument #7104 EventListenerList.add does not work #7105 EventListenerList.remove does not work #7107 DefaultBoundedRangeModel.setValue and friends should not throw And lots more. Here are answers to some questions you might have about this project and this release. 1). What is required to build/install/run? GNU Classpath requires a working GNU build environment and a byte code compiler such as jikes, gcj or kjc. When creating native code you will also need a working C compiler and up to date Gnome development libraries (gtk+, libart and gdk-pixbuf). More information on the precise version numbers for the tools and libraries can be found in the INSTALL file. A list of virtual machines and compilers known to work with GNU Classpath can be found at our website: http://www.gnu.org/software/classpath/stories.htm 2). What platforms are supported? GNU/Linux is the only platform that has been tested. We plan to eventually support many others. 3). Who should use this software? Although GNU Classpath is already capable of supporting many applications written in the java programming language, this is a development release. As such, there are still some unfinished components, and some problems are to be expected. You should install it if you are interested in GNU Classpath development or reporting bugs. We appreciate both. A good overview of the current status can be found on the GNU Classpath at FOSDEM'04 page which describes the last GNU Classpath hacker meeting. It includes reports and presentations on the current status and future plans: http://www.gnu.org/software/classpath/events/fosdem04.html 4). Where do I go for more information? The project home page with information on our mailing list can be found http://www.gnu.org/software/classpath/. signature.asc Description: This is a digitally signed message part ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
