Is there a planned date when the 04 build will become available? We want to check out the X11 Deadlock fix.
the thread was started in January, back then there wasn't a final u12 available and it was also not official that b04 would be a release build. Thats why they are talking about a ea build which never existed.
And where is the download? There is nothing to download on your link page.
( one of the first links should be: http://java.sun.com/javase/downloads/index.jsp )
Why are you calling it EA? It is a production release since Sun on its home page nowhere says it is EA and calls it an update just like it did with 6u10 and 6u11.
Actually the tab where you can get the "Latest Release" also has another tab labeled "Next Release (Early Access)" and only JDK 7 is listed.
If the distribution for download or automated update says Early Access then someone goofed in what is provided or how it is named.
That's what confused me too. That's why I asked earlier...
And before any body demonstrates their superior intelligence, look at the title for this thread.
I just want to thank you too. this was a great example how SUN listens to its users :-)
This bug caused my company some major headaches so i can't wait to get 6u12b04 in my hands!
I want to thank you also, can't wait for 6u12b04
FYI: there seems to be an unrelated snag with b04, so it may be a little delayed.
I have been able to confirm, that this bug is indeed fixed, so I hope 6u12 isn't too far away. I hope for this week or next week.
Edit: Dmitri, may I ask, if you have a new expected release date please? Can we expect it this week or next week?
Edit2: Oracle have got the FCS version of 6u12 to distribute to Forms customers from Sun, but without an installable JRE and instead the full 6u12 JDK without an installer. Can you give them an installable JRE and JDK please? As the FCS code is ready - I tested it myself by patching 6u12-beta-b03 with this version - I believe wrapping it in your installation package ought to be a simple process....
Thanks in advance,
It is availible NOW
"The full internal version number for this update release is 1.6.0_12-b04 (where "b" means "build"). The external version number is 6u12."
BTW: it's not EA, it's release.
Sun, please (!!) update the CAB file to the correct version:
This CAB file still points to some obscure old beta download. We have an automated installer system dependent on these URL for the CODEBASE parameter.
It is being updated. It will be live around 1pm.
It's the correct version now. :) Thereby I can close this case finally! Thanks for your cooperation in this matter.
I believe it should be out this week.
ixmal posted in the other thread, that bug 6784816 would make it into 6u12 in spite of earlier reports. Will it be included in b04?
Yes, b04 is the final build of 6u12, and the fix for 6784816 is included there.
Let me understand this correctly: there will be no more betas of 6u12 - the b04 release next week mentioned by Dmitri will be the final release (FCS)?
Also Artem - could I make you update bug 6784816's "Release Fixed" field to reflect this?
Thanks in advance
> Let me understand this correctly: there will be no
> more betas of 6u12 - the b04 release next week
> mentioned by Dmitri will be the final release (FCS)?
> Also Artem - could I make you update bug 6784816's
> "Release Fixed" field to reflect this?
Bugs database at bugs.sun.com doesn't reflect the full information when some bug is fixed in different JDK releases. This particular fix 6784816 is present in 6u12, but hasn't been integrated to JDK7 yet - and I suspect that's why bugs.sun.com still shows it in 'Cause known' state instead of 'Fixed'.
Actually I believe it will be shown as "fixed" on the bug parade only when it's in "integrated" state in the internal bugtraq system.
That is correct. 'Release Fixed' is tied to the 'integrated' field. That is the field that is updated when the fix is actually integrated into the master.
The link showing that it is fixed in the 6 family is below:
It seems that 6784816 is not correctly showing the link to the 2170881. I will look into why the update was not triggered. Apologies.
Great news! :) I really can't wait to test 6u12 out! I really can't thank you guys enough for letting this bugfix into 6u12 - ahead of normal schedule, as I have understood. You have solved a very big problem for me and a lot of other people involved with Oracle Forms. I'd like to buy you guys a beer, if I ever should get the chance... thanks!!!
Could I ask one of you guys a favor - to update Sun case #66165649 with this information? This is the case Oracle logged on this bug, and they would really like a confirmation through their "official" channel, which is this case, that the bug is indeed fixed in 6u12.
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Participation.
Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.