From Joe.Darcy at Sun.COM Mon Feb 11 11:43:40 2008 From: Joe.Darcy at Sun.COM (Joseph D. Darcy) Date: Mon, 11 Feb 2008 11:43:40 -0800 Subject: "The code is coming! The code is coming!" Message-ID: <47B0A56C.8070704@sun.com> Greetings. At Sun we're making final preparations for the first source release for the OpenJDK 6 project. We plan to release a tarball of the source, along with matching binary plugs, by February 15, 2008. The tarball will be a not-quite-finished backward branch to the Java SE 6 API [1]. In addition to discussions around completing the work on that branch, I also consider technical discussions of issues related to getting the code building and running on different platforms to be on-topic for this alias. The source for OpenJDK 6 will eventually live in its own forest of Mercurial repositories; however, at the moment there is some remaining in-progress engineering work to get done in the near future and it is more efficient for the Sun-internal teamware workspaces to remain the master copy of the source for the time being. One such in-progress change is upgrading JAX-WS from 2.0 to 2.1. (As an endorsed standard [2], the version of JAX-WS shipped in a JDK can be upgraded; the JAX-WS 2.0 -> 2.1 upgrade was also done in Sun's JDK 6 update 4 [3].) External contributions for changes to OpenJDK 6 should go through the established channels [2]. The frequency of subsequent source drops will depend on the rate of change in the code. The code has the some general directory and build structure as the JDK 7 sources. Besides undoing most of the JDK 7 API changes, this first code release has fixes to various other bugs including: 6598089 JDK 7: AWT often goes into busy loop when showing dialog 6612531 api/javax_swing/ScrollPaneLayout/index.html#xxxLayoutSize [ScrollPaneLayout2024] throws NPE 6532373 xcb_xlib.c:50: xcb_xlib_unlock: Assertion 'c->xlib.lock' failed. 6643627 JMX source code includes incorrect Java code -Joe [1] http://blogs.sun.com/darcy/entry/forward_to_the_past [2] http://java.sun.com/javase/6/docs/technotes/guides/standards/index.html [3] http://weblogs.java.net/blog/ramapulavarthi/archive/2008/01/jaxws_21_and_ja.html [4] http://openjdk.java.net/contribute/ From mark at klomp.org Mon Feb 11 12:11:25 2008 From: mark at klomp.org (Mark Wielaard) Date: Mon, 11 Feb 2008 21:11:25 +0100 Subject: "The code is coming! The code is coming!" In-Reply-To: <47B0A7D2.5080106@sun.com> References: <47B0A7D2.5080106@sun.com> Message-ID: <1202760685.3821.11.camel@dijkstra.wildebeest.org> Hi Joe, On Mon, 2008-02-11 at 11:53 -0800, Joseph D. Darcy wrote: > At Sun we're making final preparations for the first source release for > the OpenJDK 6 project. We plan to release a tarball of the source, > along with matching binary plugs, by February 15, 2008. The tarball > will be a not-quite-finished backward branch to the Java SE 6 API [1]. Great! Really looking forward to this. > The source for OpenJDK 6 will eventually live in its own forest of > Mercurial repositories Any ETA on this? I ask because it makes sense for IcedTea to track this instead of the jdk7 variant. And obviously it is easier to provide patches against a me mercurial tree (or work on your own patch set). Alternatively if you intend to push out tar ball drops for some time would it make sense for me to setup a mercurial mirror that just imports those releases when they happen? (We did this earlier when openjdk only had subversion support and we already wanted mercurial access for icedtea). > Besides undoing most of the JDK 7 API changes, this first code release > has fixes to various other bugs including: > > 6598089 JDK 7: AWT often goes into busy loop when showing dialog Excellent! Just for this I owe you several virtual beers! This bug has frustrated me so much. Thank you! Thank you! Thank you! Cheers, Mark From Joe.Darcy at Sun.COM Mon Feb 11 14:25:46 2008 From: Joe.Darcy at Sun.COM (Joseph D. Darcy) Date: Mon, 11 Feb 2008 14:25:46 -0800 Subject: "The code is coming! The code is coming!" In-Reply-To: <1202760685.3821.11.camel@dijkstra.wildebeest.org> References: <47B0A7D2.5080106@sun.com> <1202760685.3821.11.camel@dijkstra.wildebeest.org> Message-ID: <47B0CB6A.10508@sun.com> Mark Wielaard wrote: > Hi Joe, > > On Mon, 2008-02-11 at 11:53 -0800, Joseph D. Darcy wrote: >> At Sun we're making final preparations for the first source release for >> the OpenJDK 6 project. We plan to release a tarball of the source, >> along with matching binary plugs, by February 15, 2008. The tarball >> will be a not-quite-finished backward branch to the Java SE 6 API [1]. > > Great! Really looking forward to this. Me too! :-) >> The source for OpenJDK 6 will eventually live in its own forest of >> Mercurial repositories > > Any ETA on this? I ask because it makes sense for IcedTea to track this > instead of the jdk7 variant. And obviously it is easier to provide > patches against a me mercurial tree (or work on your own patch set). I would expect the tarballs to persist at least through March. > Alternatively if you intend to push out tar ball drops for some time > would it make sense for me to setup a mercurial mirror that just imports > those releases when they happen? (We did this earlier when openjdk only > had subversion support and we already wanted mercurial access for > icedtea). > >> Besides undoing most of the JDK 7 API changes, this first code release >> has fixes to various other bugs including: >> >> 6598089 JDK 7: AWT often goes into busy loop when showing dialog > > Excellent! Just for this I owe you several virtual beers! This bug has > frustrated me so much. Thank you! Thank you! Thank you! Glad to help; I won't be going to FOSDEM this year, but I'll be downing some Hoegaarden that weekend to keep in the spirit :-) -Joe From Joe.Darcy at Sun.COM Thu Feb 14 11:01:16 2008 From: Joe.Darcy at Sun.COM (Joseph D. Darcy) Date: Thu, 14 Feb 2008 11:01:16 -0800 Subject: "The code is coming! The code is coming!" -- "The code is here!!" In-Reply-To: <47B0A56C.8070704@sun.com> References: <47B0A56C.8070704@sun.com> Message-ID: <47B48FFC.8010600@sun.com> The initial in-progress code, with matching plugs, is now available: http://download.java.net/openjdk/jdk6/ (Yay!) The project page will be updated with a pointer shortly. As for what's already in the works for near-future builds, in addition to the JAX-WS 2.0 -> 2.1 upgrade, Phil will be working on removing the binary plug for the imaging classes [1], the JMX team is working on changing the build to exclude SNMP support if the binary plugs aren't present, and I'll be updating the README-builds file to point at the right locations. I'd expect the next source drop within two weeks, probably sooner. Happy hacking, -Joe [1] http://mail.openjdk.java.net/pipermail/discuss/2008-February/001078.html Joseph D. Darcy wrote: > Greetings. > > At Sun we're making final preparations for the first source release for > the OpenJDK 6 project. We plan to release a tarball of the source, > along with matching binary plugs, by February 15, 2008. The tarball > will be a not-quite-finished backward branch to the Java SE 6 API [1]. > > In addition to discussions around completing the work on that branch, I > also consider technical discussions of issues related to getting the > code building and running on different platforms to be on-topic for this > alias. > > The source for OpenJDK 6 will eventually live in its own forest of > Mercurial repositories; however, at the moment there is some remaining > in-progress engineering work to get done in the near future and it is > more efficient for the Sun-internal teamware workspaces to remain the > master copy of the source for the time being. One such in-progress > change is upgrading JAX-WS from 2.0 to 2.1. (As an endorsed standard > [2], the version of JAX-WS shipped in a JDK can be upgraded; the JAX-WS > 2.0 -> 2.1 upgrade was also done in Sun's JDK 6 update 4 [3].) External > contributions for changes to OpenJDK 6 should go through the established > channels [2]. > > The frequency of subsequent source drops will depend on the rate of > change in the code. The code has the some general directory and build > structure as the JDK 7 sources. > > Besides undoing most of the JDK 7 API changes, this first code release > has fixes to various other bugs including: > > 6598089 JDK 7: AWT often goes into busy loop when showing dialog > 6612531 api/javax_swing/ScrollPaneLayout/index.html#xxxLayoutSize > [ScrollPaneLayout2024] throws NPE > 6532373 xcb_xlib.c:50: xcb_xlib_unlock: Assertion 'c->xlib.lock' failed. > 6643627 JMX source code includes incorrect Java code > > -Joe > > [1] http://blogs.sun.com/darcy/entry/forward_to_the_past > [2] http://java.sun.com/javase/6/docs/technotes/guides/standards/index.html > [3] > http://weblogs.java.net/blog/ramapulavarthi/archive/2008/01/jaxws_21_and_ja.html > > [4] http://openjdk.java.net/contribute/ From Joe.Darcy at Sun.COM Thu Feb 14 11:04:25 2008 From: Joe.Darcy at Sun.COM (Joseph D. Darcy) Date: Thu, 14 Feb 2008 11:04:25 -0800 Subject: Some thoughts on the project's code evolution Message-ID: <47B490B9.4000507@sun.com> A few thoughts on the evolution of the code base, I estimate most of the remaining work for a fully open source and fully compatible Java SE 6 implementation will be in the "jdk" area of the code, mostly the Java source for java.* and javax.* packages. I think this project's efforts should be focused on clearing encumbrances and achieving compliance. So as far as the VM goes, for OpenJDK 6 I think using a recent, but not bleeding edge, HotSpot may be the appropriate choice. Unlike with the library code in the JDK 6 update and JDK 7 releases, the HotSpot team is trying out a somewhat different release model where they essentially use the some code base for both release families. (Adopting this cross-version reuse is much more tractable in a component like HotSpot without many exported external interfaces, in contrast to the java.* and javax.* API.) I'd recommend people interested in hacking the VM to work directly with the HotSpot team [1], with changes percolating back to OpenJDK 6 once they are fully vetted. For example, the OpenJDK 6 HotSpot might be kept in sync with the version used in the latest shipping JDK 6 update release. Today the initial source bundle for OpenJDK 6 is using the same HotSpot source as the recently-released JDK 6 update 4 (with the addition of a small patch to build under gcc 4). The bleeding edge alternative would be to use the JDK 7 HotSpot Mercurial repository as the OpenJDK 6 Mercurial repository too, after the OpenJDK 6 Mercurial transition. Comments? -Joe [1] http://openjdk.java.net/groups/hotspot/ From Joe.Darcy at Sun.COM Fri Feb 15 10:12:33 2008 From: Joe.Darcy at Sun.COM (Joseph D. Darcy) Date: Fri, 15 Feb 2008 10:12:33 -0800 Subject: FYI: New IcedTea6 Repository Message-ID: <47B5D611.8070603@sun.com> New IcedTea6 repository using the OpenJDK 6 source: http://icedtea.classpath.org/hg/icedtea6 More information on http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2008-February/001192.html -Joe From bha at att.net Sun Feb 17 18:51:33 2008 From: bha at att.net (bha@worldnet.att.net) Date: Mon, 18 Feb 2008 02:51:33 +0000 Subject: 6486887: (prefs) Preferences sync fails if jaxp transform provider doesn't support indent-number Message-ID: <021820080251.10355.47B8F2B50004D9B60000287322243429029B0A02D29B9B0EBF0E080D@att.net> I'm planning to look into providing a back-port patch for this bug. It is marked as fixed in jdk 7, but a bunch of us really need it fixed in jdk 6 too. This Preferences Impl bug is a regression, as it works fine in jdk 5. That said, is anybody else already working on this, and/or any words of warning/wisdom/advice? Thanks, Dan Rollo From Joe.Darcy at Sun.COM Sun Feb 17 19:17:52 2008 From: Joe.Darcy at Sun.COM (Joseph D. Darcy) Date: Sun, 17 Feb 2008 19:17:52 -0800 Subject: 6486887: (prefs) Preferences sync fails if jaxp transform provider doesn't support indent-number In-Reply-To: <021820080251.10355.47B8F2B50004D9B60000287322243429029B0A02D29B9B0EBF0E080D@att.net> References: <021820080251.10355.47B8F2B50004D9B60000287322243429029B0A02D29B9B0EBF0E080D@att.net> Message-ID: <47B8F8E0.8090103@sun.com> bha at worldnet.att.net wrote: > I'm planning to look into providing a back-port patch for this bug. It is marked as fixed in jdk 7, but a bunch of us really need it fixed in jdk 6 too. This Preferences Impl bug is a regression, as it works fine in jdk 5. > > That said, is anybody else already working on this, and/or any words of warning/wisdom/advice? > Hello. The issue in question was fixed under 6396599 (prefs) Preferences sync fails if jaxp transform provider doesn't support indent-number early in JDK 7 and the fix should also be in the OpenJDK 6 sources. The OpenJDK 6 sources branched off from JDK 7 around build 20, circa late August 2007 to early September 2007. If a fix was in JDK 7 before then, it should also be in OpenJDK 6. Regards, -Joe From bha at att.net Sun Feb 17 20:06:47 2008 From: bha at att.net (bha@worldnet.att.net) Date: Mon, 18 Feb 2008 04:06:47 +0000 Subject: 6486887: (prefs) Preferences sync fails if jaxp transform provider doesn't support indent-number Message-ID: <021820080406.9537.47B904570008B8A80000254122243323629B0A02D29B9B0EBF0E080D@att.net> -------------- Original message ---------------------- From: "Joseph D. Darcy" > > bha at worldnet.att.net wrote: > > I'm planning to look into providing a back-port patch for this bug. It is > marked as fixed in jdk 7, but a bunch of us really need it fixed in jdk 6 too. > This Preferences Impl bug is a regression, as it works fine in jdk 5. > > > > That said, is anybody else already working on this, and/or any words of > warning/wisdom/advice? > > > > Hello. > > The issue in question was fixed under > > 6396599 (prefs) Preferences sync fails if jaxp transform provider > doesn't support indent-number > > early in JDK 7 and the fix should also be in the OpenJDK 6 sources. The > OpenJDK 6 sources branched off from JDK 7 around build 20, circa late > August 2007 to early September 2007. If a fix was in JDK 7 before then, > it should also be in OpenJDK 6. > > Regards, > > -Joe Hi Joe, Judging from the source in the newly published jdk6 bundle (b05-12_feb_2008), it appears the fix for this bug is included: file: java/util/prefs/XmlSupport /** * Write XML document to the specified output stream. */ private static final void writeDoc(Document doc, OutputStream out) throws IOException { try { TransformerFactory tf = TransformerFactory.newInstance(); try { tf.setAttribute("indent-number", new Integer(2)); } catch (IllegalArgumentException iae) { //Ignore the IAE. Should not fail the writeout even the //transformer provider does not support "indent-number". } ... Cool. Now how do I figure out when/if this code will make it into a release of jdk/jre 1.6? Dare I infer the "b05" might translate to jdk6 update 5? Thanks, Dan From Joe.Darcy at Sun.COM Sun Feb 17 20:51:52 2008 From: Joe.Darcy at Sun.COM (Joseph D. Darcy) Date: Sun, 17 Feb 2008 20:51:52 -0800 Subject: 6486887: (prefs) Preferences sync fails if jaxp transform provider doesn't support indent-number In-Reply-To: <021820080406.9537.47B904570008B8A80000254122243323629B0A02D29B9B0EBF0E080D@att.net> References: <021820080406.9537.47B904570008B8A80000254122243323629B0A02D29B9B0EBF0E080D@att.net> Message-ID: <47B90EE8.4040901@sun.com> bha at worldnet.att.net wrote: > -------------- Original message ---------------------- > From: "Joseph D. Darcy" >> bha at worldnet.att.net wrote: >>> I'm planning to look into providing a back-port patch for this bug. It is >> marked as fixed in jdk 7, but a bunch of us really need it fixed in jdk 6 too. >> This Preferences Impl bug is a regression, as it hworks fine in jdk 5. >>> That said, is anybody else already working on this, and/or any words of >> warning/wisdom/advice? >>> >> Hello. >> >> The issue in question was fixed under >> >> 6396599 (prefs) Preferences sync fails if jaxp transform provider >> doesn't support indent-number >> >> early in JDK 7 and the fix should also be in the OpenJDK 6 sources. The >> OpenJDK 6 sources branched off from JDK 7 around build 20, circa late >> August 2007 to early September 2007. If a fix was in JDK 7 before then, >> it should also be in OpenJDK 6. >> >> Regards, >> >> -Joe > > > Hi Joe, > > Judging from the source in the newly published jdk6 bundle (b05-12_feb_2008), it appears the fix for this bug is included: > > file: java/util/prefs/XmlSupport > > /** > * Write XML document to the specified output stream. > */ > private static final void writeDoc(Document doc, OutputStream out) > throws IOException > { > try { > TransformerFactory tf = TransformerFactory.newInstance(); > try { > tf.setAttribute("indent-number", new Integer(2)); > } catch (IllegalArgumentException iae) { > //Ignore the IAE. Should not fail the writeout even the > //transformer provider does not support "indent-number". > } > ... > > Cool. Now how do I figure out when/if this code will make it into a release of jdk/jre 1.6? Dare I infer the "b05" might translate to jdk6 update 5? Hello. That is a separate question. OpenJDK 6 and Sun's 6 updates are different, but related, release trains. The "b05" in this case is build 5 of OpenJDK 6, which has no direct relation to 6 update 5. I'll be posting some thoughts on criteria for getting bug fixes into OpenJDK 6 versus JDK 7 versus a 6 update release in the near future. However, to get 6396599 fixed in a 6 update release, I suggest you and others interested in a fix add votes for the bug on bugs.sun.com; I'll also forward this issue to those who run the 6 update releases. Cheers, -Joe From bha at att.net Mon Feb 18 17:11:56 2008 From: bha at att.net (bha@worldnet.att.net) Date: Tue, 19 Feb 2008 01:11:56 +0000 Subject: 6486887: (prefs) Preferences sync fails if jaxp transform provider doesn't support indent-number Message-ID: <021920080111.20513.47BA2CDC0003C7B10000502122218675169B0A02D29B9B0EBF0E080D@att.net> -------------- Original message ---------------------- From: "Joseph D. Darcy" > > bha at worldnet.att.net wrote: > > -------------- Original message ---------------------- > > From: "Joseph D. Darcy" > >> bha at worldnet.att.net wrote: > >>> I'm planning to look into providing a back-port patch for this bug. It is > >> marked as fixed in jdk 7, but a bunch of us really need it fixed in jdk 6 > too. > >> This Preferences Impl bug is a regression, as it hworks fine in jdk 5. > >>> That said, is anybody else already working on this, and/or any words of > >> warning/wisdom/advice? > >>> > >> Hello. > >> > >> The issue in question was fixed under > >> > >> 6396599 (prefs) Preferences sync fails if jaxp transform provider > >> doesn't support indent-number > >> > >> early in JDK 7 and the fix should also be in the OpenJDK 6 sources. The > >> OpenJDK 6 sources branched off from JDK 7 around build 20, circa late > >> August 2007 to early September 2007. If a fix was in JDK 7 before then, > >> it should also be in OpenJDK 6. > >> > >> Regards, > >> > >> -Joe > > > > > > Hi Joe, > > > > Judging from the source in the newly published jdk6 bundle (b05-12_feb_2008), > it appears the fix for this bug is included: > > > > file: java/util/prefs/XmlSupport > > > > /** > > * Write XML document to the specified output stream. > > */ > > private static final void writeDoc(Document doc, OutputStream out) > > throws IOException > > { > > try { > > TransformerFactory tf = TransformerFactory.newInstance(); > > try { > > tf.setAttribute("indent-number", new Integer(2)); > > } catch (IllegalArgumentException iae) { > > //Ignore the IAE. Should not fail the writeout even the > > //transformer provider does not support "indent-number". > > } > > ... > > > > Cool. Now how do I figure out when/if this code will make it into a release of > jdk/jre 1.6? Dare I infer the "b05" might translate to jdk6 update 5? > > Hello. > > That is a separate question. OpenJDK 6 and Sun's 6 updates are > different, but related, release trains. The "b05" in this case is > build 5 of OpenJDK 6, which has no direct relation to 6 update 5. I'll > be posting some thoughts on criteria for getting bug fixes into OpenJDK > 6 versus JDK 7 versus a 6 update release in the near future. However, > to get 6396599 fixed in a 6 update release, I suggest you and others > interested in a fix add votes for the bug on bugs.sun.com; I'll also > forward this issue to those who run the 6 update releases. > > Cheers, > > -Joe Hi Joe, I see, and I appreciate you forwarding this to the Sun JDK 6 update team very much. One problem with this sort of back port regarding voting: As is often the case, all the bug reports are closed, marked as "fixed" in a newer release, while still being broken in the currently most common real world release. That is the case here as well. The bugs are all closed as duplicates and/or closed as fixed in JDK 7. 6396599 http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6396599 6486887 http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6486887 6568540 http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6568540 The problem is we can't vote for closed bugs (and even if we could, I doubt the votes would be considered as important...) Though the bugs are closed, there are a bunch of user comments asking about a JDK 6 back port. Would you suggest I open a brand new bug report specific to JDK 6 for this, or does that just add noise? Thanks, Dan From lists at munckfish.net Wed Feb 27 04:20:48 2008 From: lists at munckfish.net (Dan Munckton) Date: Wed, 27 Feb 2008 12:20:48 +0000 Subject: com.sun.image.codec.jpeg.* classes missing from bin plugs and open sources Message-ID: <1204114849.10820.9.camel@dylan> Hi I've discovered (because an app I'm maintaining seems to be using JPEGCodec and JPEGImageEncoder) that the classes under com.sun.image.codec.jpeg.* are missing from the OpenJDK 6 & 7 builds. They're not in the sources nor in the binary plugs. Googling I find that stubs have been implemented in the IcedTea sources. Can anyone explain what the situation is with these classes? Should they be in the bin plugs or are they on the way out completely? Cheers Dan From mr at sun.com Thu Feb 28 08:42:13 2008 From: mr at sun.com (Mark Reinhold) Date: Thu, 28 Feb 2008 08:42:13 -0800 Subject: HotSpot C++ interpreter? Message-ID: <20080228164213.1422B2789B5@eggemoggin.niobe.net> How hard would it be to merge the C++ interpreter from 7 back to 6? Andrew Haley of Red Hat tells me that it's important to have it so that Gary Benson's "zero-assembler" port can be used on architectures to which HotSpot hasn't yet been ported. I'd hope it'd be straightforward, but I could be wrong ... - Mark From Joe.Darcy at Sun.COM Thu Feb 28 17:36:02 2008 From: Joe.Darcy at Sun.COM (Joseph D. Darcy) Date: Thu, 28 Feb 2008 17:36:02 -0800 Subject: Next code drop of OpenJDK 6 on track for February 29, 2008 Message-ID: <47C76182.4070901@sun.com> Hello. We're on track to publish the second code drop of OpenJDK 6, b06, on February 29, 2008. This drop will have a few fixes of note: As previous announced, Phil Race has moved the imaging classes from closed to open, reducing the need for the binary plugs: 6662775 Move Imaging and color classes from closed to open The JAX-WS 2.0 -> 2.1 upgrade with associated changes: 6605798 JAX-WS RI 2.1.1 should be integrated in OpenJDK6. The JMX team has modified the build so that the SNMP portion of the build will not fail if the binary plug isn't present, with the caveat that without the plug SNMP won't work at runtime: 6661448 Make the SNMP agent optional when OPENJDK=true and IMPORT_BINARY_PLUGS=false Various l10n and i18n fixes including: 6573250 Java.util.Currency.getSymbol(Locale) returns wrong value when locale is not US. I applied the change to freshen the time zone information: 6646197 (tz) Support tzdata2007k Also of note is the inclusion of a trademark license for "OpenJDK." Things in the works for b07 include a port of the fix for 6586752 "No window decorations (title bar etc.) x86_64" and a change to the build so that the build can succeed if no binary plugs are present (stubbed out midi synthesizer classes will most likely be used to make this happen). I expect b07 within two weeks. Enjoy, -Joe From pdoubleya at gmail.com Fri Feb 29 00:30:14 2008 From: pdoubleya at gmail.com (Patrick Wright) Date: Fri, 29 Feb 2008 09:30:14 +0100 Subject: OpenJDK/Java 6 and Update N Message-ID: <64efa1ba0802290030h450af42h53ad22b2e7e987ea@mail.gmail.com> Hi I'm wondering on how changes flowing into "update N" will be synchronized with the OpenJDK/Java 6 repository, and if there is a schedule for when this will happen, and for when they will be kept permanently in sync. Thanks! Patrick From Joe.Darcy at Sun.COM Fri Feb 29 09:47:50 2008 From: Joe.Darcy at Sun.COM (Joseph D. Darcy) Date: Fri, 29 Feb 2008 09:47:50 -0800 Subject: Next code drop of OpenJDK 6 on track for February 29, 2008 In-Reply-To: <47C76182.4070901@sun.com> References: <47C76182.4070901@sun.com> Message-ID: <47C84546.6090807@sun.com> The b06 source is now available: http://download.java.net/openjdk/jdk6/ -Joe Joseph D. Darcy wrote: > Hello. > > We're on track to publish the second code drop of OpenJDK 6, b06, on > February 29, 2008. > > This drop will have a few fixes of note: > > As previous announced, Phil Race has moved the imaging classes from > closed to open, reducing the need for the binary plugs: > 6662775 Move Imaging and color classes from closed to open > > The JAX-WS 2.0 -> 2.1 upgrade with associated changes: > 6605798 JAX-WS RI 2.1.1 should be integrated in OpenJDK6. > > The JMX team has modified the build so that the SNMP portion of the > build will not fail if the binary plug isn't present, with the caveat > that without the plug SNMP won't work at runtime: > 6661448 Make the SNMP agent optional when OPENJDK=true and > IMPORT_BINARY_PLUGS=false > > Various l10n and i18n fixes including: > 6573250 Java.util.Currency.getSymbol(Locale) returns wrong value when > locale is not US. > > I applied the change to freshen the time zone information: > 6646197 (tz) Support tzdata2007k > > Also of note is the inclusion of a trademark license for "OpenJDK." > > Things in the works for b07 include a port of the fix for 6586752 > "No window decorations (title bar etc.) x86_64" and a change to the > build so that the build can succeed if no binary plugs are present > (stubbed out midi synthesizer classes will most likely be used to make > this happen). > > I expect b07 within two weeks. > > Enjoy, > > -Joe