Hi all, As some people have been saying already there were some impressive showcases at Fosdem of things that just work now. So I feel it is time to do a new snapshot this week to share all this great work with our users. Both awt and swing made some very nice improvements, we have all the new crypto algorithms now (https support out of the box), new rmi/corba tools, unicode 4.0 support, (VM)Math improvements, regex improvements, and probably lots of other things I am forgetting now. (Please update the NEWS file!)
It looks like we are in pretty good shape. Some smoke-tests with some simple applications work nicely for me. And Mauve gives us this impressive score: classpath-0.20 38115 PASS 983 FAIL classpath-0.21-pre 43615 PASS 583 FAIL There are some regressions that builder didn't seem to have picked up though (attached). We need to go through these to see whether they are fatal/embarrassing. Other things to do: - Update the NEWS file! - Test more apps. - Go through the bug-list for "must fix" things. - Remerge CVS trunk with the generics branch (I don't know whether Andrew has had time for that since his Math work. Please yell and scream if you need help with this Andrew.) - Make builder produce a real classpath-generics dist again. (I'll try to take a look at that tonight.) - Decide on the version number. We had a very small/brief discussion about this during Fosdem. Everybody seems to agree 0.x really doesn't do justice to the maturity we have reached over the years. And it is really hard to define when we hit "1.0". So the proposal is to keep using a "sequence version number". Either just drop the "0." and make the next release-number classpath-21, or adopt a year.month style version number and make the next version number classpath-6.3 for the March 2006 release. In either case we will just use a code name for a release that has some special feature set that we are proud of, but we will always just increase the release snapshot number. Suggestions or Opinions? Different from previous releases I will probably create a branch for this one. If things look basically OK, I'll create that on Wednesday and then test that and back-port patches from CVS trunk to it till it is "perfect". That makes sure other people can just happily go on hacking. Please let me know if there is something you feel would be really nice to have in for this release. Cheers, Mark
-PASS: gnu.testlet.javax.swing.JLabel.Icon (number 6) -PASS: gnu.testlet.javax.swing.JLabel.Icon (number 7) +FAIL: gnu.testlet.javax.swing.JLabel.Icon (number 6) +FAIL: gnu.testlet.javax.swing.JLabel.Icon (number 7) -PASS: gnu.testlet.javax.swing.text.AbstractDocument.BranchElement.getElementIndexNullPointer (number 1) +FAIL: gnu.testlet.javax.swing.text.AbstractDocument.BranchElement.getElementIndexNullPointer: AbstractDocument.BranchElement.getElementIndex should throw NPE when it has no children (number 1) +FAIL: gnu.testlet.javax.swing.text.AbstractDocument.ElementChange: uncaught exception: java.lang.NullPointerException +FAIL: uncaught exception loading gnu.testlet.javax.swing.text.DefaultStyledDocument.ElementBuffer.StyledDocument2: java.lang.NullPointerException +FAIL: uncaught exception loading gnu.testlet.javax.swing.text.DefaultStyledDocument.ElementBuffer.StyledDocument3: java.lang.NullPointerException -PASS: gnu.testlet.javax.swing.text.MaskFormatter.MaskFormatterTest: valid output (number 7) +FAIL: gnu.testlet.javax.swing.text.MaskFormatter.MaskFormatterTest: uncaught exception at "valid output" number 2: java.lang.NullPointerException -PASS: gnu.testlet.javax.swing.SwingUtilities.layoutCompoundLabel: TC-text (number 3) +FAIL: gnu.testlet.javax.swing.SwingUtilities.layoutCompoundLabel: TC-text (number 3) -PASS: gnu.testlet.javax.swing.SwingUtilities.layoutCompoundLabel: TR-text (number 3) +FAIL: gnu.testlet.javax.swing.SwingUtilities.layoutCompoundLabel: TR-text (number 3) -PASS: gnu.testlet.javax.swing.SwingUtilities.layoutCompoundLabel: CL-text (number 2) +FAIL: gnu.testlet.javax.swing.SwingUtilities.layoutCompoundLabel: CL-text (number 2) -PASS: gnu.testlet.javax.swing.SwingUtilities.layoutCompoundLabel: CC-text (number 2) -PASS: gnu.testlet.javax.swing.SwingUtilities.layoutCompoundLabel: CC-text (number 3) +FAIL: gnu.testlet.javax.swing.SwingUtilities.layoutCompoundLabel: CC-text (number 2) +FAIL: gnu.testlet.javax.swing.SwingUtilities.layoutCompoundLabel: CC-text (number 3) -PASS: gnu.testlet.javax.swing.SwingUtilities.layoutCompoundLabel: CR-text (number 3) +FAIL: gnu.testlet.javax.swing.SwingUtilities.layoutCompoundLabel: CR-text (number 3) -PASS: gnu.testlet.javax.swing.SwingUtilities.layoutCompoundLabel: BC-text (number 3) +FAIL: gnu.testlet.javax.swing.SwingUtilities.layoutCompoundLabel: BC-text (number 3) -PASS: gnu.testlet.javax.swing.SwingUtilities.layoutCompoundLabel: BR-text (number 3) +FAIL: gnu.testlet.javax.swing.SwingUtilities.layoutCompoundLabel: BR-text (number 3) -PASS: gnu.testlet.javax.swing.plaf.metal.MetalComboBoxUI.getDisplaySize (number 2) -PASS: gnu.testlet.javax.swing.plaf.metal.MetalComboBoxUI.getDisplaySize (number 3) -PASS: gnu.testlet.javax.swing.plaf.metal.MetalComboBoxUI.getDisplaySize (number 4) +FAIL: gnu.testlet.javax.swing.plaf.metal.MetalComboBoxUI.getDisplaySize (number 2) +FAIL: gnu.testlet.javax.swing.plaf.metal.MetalComboBoxUI.getDisplaySize (number 3) +FAIL: gnu.testlet.javax.swing.plaf.metal.MetalComboBoxUI.getDisplaySize (number 4) -PASS: gnu.testlet.javax.swing.plaf.basic.BasicComboBoxUI.getMinimumSize (number 2) -PASS: gnu.testlet.javax.swing.plaf.basic.BasicComboBoxUI.getMinimumSize (number 3) +FAIL: gnu.testlet.javax.swing.plaf.basic.BasicComboBoxUI.getMinimumSize (number 2) +FAIL: gnu.testlet.javax.swing.plaf.basic.BasicComboBoxUI.getMinimumSize (number 3) -PASS: gnu.testlet.javax.swing.plaf.basic.BasicComboBoxUI.getPreferredSize (number 2) -PASS: gnu.testlet.javax.swing.plaf.basic.BasicComboBoxUI.getPreferredSize (number 3) +FAIL: gnu.testlet.javax.swing.plaf.basic.BasicComboBoxUI.getPreferredSize (number 2) +FAIL: gnu.testlet.javax.swing.plaf.basic.BasicComboBoxUI.getPreferredSize (number 3) -PASS: gnu.testlet.javax.swing.plaf.basic.BasicComboBoxUI.getDisplaySize (number 2) -PASS: gnu.testlet.javax.swing.plaf.basic.BasicComboBoxUI.getDisplaySize (number 3) -PASS: gnu.testlet.javax.swing.plaf.basic.BasicComboBoxUI.getDisplaySize (number 4) +FAIL: gnu.testlet.javax.swing.plaf.basic.BasicComboBoxUI.getDisplaySize (number 2) +FAIL: gnu.testlet.javax.swing.plaf.basic.BasicComboBoxUI.getDisplaySize (number 3) +FAIL: gnu.testlet.javax.swing.plaf.basic.BasicComboBoxUI.getDisplaySize (number 4) Weird exception: gnu.testlet.gnu.javax.swing.text.html.parser.support.Parser.HTML_parsing gnu.testlet.gnu.javax.swing.text.html.parser.support.Parser.HTML_randomTable
signature.asc
Description: This is a digitally signed message part
