Java 6 update 10 is released

[swpalmer]

With no announcement on java.net or java.sun.com

[emzic]

yeah, it looks like it is released on java.sun.com, but is it for real?
just recently i read on the java.net forums about some pretty serious bugs in 6u10.

[princec]

Must be a quiet release then to pick up any major "oooh f*ck!" problems. I'll go and grab it now...

Cas

Games published by our own members! Check 'em out!

[emzic]

Must be a quiet release then to pick up any major "oooh f*ck!" problems. I'll go and grab it now...

speaking of oh f*ck, i just noticed that my jogl-game flickers badly when i resize the window (awt-frame) in java6u10 while it works smoothly in java6u7.

[princec]

Deary me. It seems to be the release candidate that's why the've not announced it:

1   2   3   4   5

java -version java version "1.6.0_10-rc" Java(TM) SE Runtime Environment (build 1.6.0_10-rc-b28) Java HotSpot(TM) Client VM (build 11.0-b15, mixed mode, sharing)

Cas

[Jackal von ÖRF]

The release candidate was released earlier. This looks like the real thing.

>java -version
java version "1.6.0_10"
Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
Java HotSpot(TM) Client VM (build 11.0-b15, mixed mode, sharing)

[princec]

How much earlier? I literally downloaded it a couple of hours ago.

Cas

[endolf]

1   2   3   4

java -version java version "1.6.0_10-rc" Java(TM) SE Runtime Environment (build 1.6.0_10-rc-b28) Java HotSpot(TM) Client VM (build 11.0-b15, mixed mode, sharing)

Date stamp on the installer is 19/8/2008, but the file itself is jdk-6u10-rc-bin-b28-windows-i586-p-21_jul_2008.exe

Endolf

[EgonOlsen]

Bad news for me and all other pixel pusher. The new d3d-pipeline for Windows still sucks when it comes to blitting BufferedImages to screen that aren't static. More information: http://bugs.sun.com/view_bug.do?bug_id=6652116

[swpalmer]

1   2   3   4

java -version java version "1.6.0_10-rc" Java(TM) SE Runtime Environment (build 1.6.0_10-rc-b28) Java HotSpot(TM) Client VM (build 11.0-b15, mixed mode, sharing)

Date stamp on the installer is 19/8/2008, but the file itself is jdk-6u10-rc-bin-b28-windows-i586-p-21_jul_2008.exe

Endolf

That's way behind.  I don't even think that is RC2.  I was running 6u10rc-b32 for a while before installing the b33 "release" yesterday.
You got this from java.sun.com ?

Games published by our own members! Check 'em out!

[DzzD]

Bad news for me and all other pixel pusher. The new d3d-pipeline for Windows still sucks when it comes to blitting BufferedImages to screen that aren't static. More information: http://bugs.sun.com/view_bug.do?bug_id=6652116

bug voted,

thanks for the information... and once again that's too bad...  so much regression...

[zammbi]

Yes, not good news about that.
Seems the priority is low, so I don't see that being fixed anytime soon.

[endolf]

That's way behind.  I don't even think that is RC2.  I was running 6u10rc-b32 for a while before installing the b33 "release" yesterday.
You got this from java.sun.com ?

I didn't, but apparently cas did, the output from java -version matches what he was saying he had downloaded.

Endolf

[bienator]

downloaded&installed today and its build 33. Build 28 would be pretty strange since it had some issues with draggable applets which is more or less together with the new plugin the main feature regarding desktop java.

in case you think you got the wrong data, download again ;-)

[ChrisM]

AHEM - it has not passed the attention of Sun that there was no comment with this release.  Expect to hear from Sun next week

[princec]

Oh well I'll wait until it's announced and get it then. Or -- will the autoupdater do it for me? (Not that it'll get the JDK but I'd like to see the JRE get it right for once!)

Cas

[Riven]

Aaaah... the JavaWebStart 'it worked the second time' is still there!


Further, it displays the "Could not launch your application" (+stacktrace + jnlp code) if your app throws ANY exception at ANY time (like when closing down after 30 minutes) in the mainthread (?)

And it stops launching your app (!) when the SPLASH image could not be found.... hrrr!


Go go go!

[Mr. Gol]

AHEM - it has not passed the attention of Sun that there was no comment with this release.  Expect to hear from Sun next week

So the "never release anything on a friday" rule is used at Sun as well

[zammbi]

I download the JDK version, and it didn't fully update. My about box still showed it was still RC. Installing the JRE fixed the problem.

[bienator]

So the "never release anything on a friday" rule is used at Sun as well

I guess the webmasters are not synchronized with the rest of Sun.

[swpalmer]

So the "never release anything on a friday" rule is used at Sun as well

It was released on a Thursday :-)

As for Exceptions and missing Splash images causing issues with WebStart - I would consider that very low priority - I mean, come on... fix YOUR bugs first.

The "Works the second time" thing sounds like a much bigger deal.. does anyone have a bug # for that one?

[Riven]

Hehe, not my bugs, I noticed it on somebodyelses JWS app.


I haven't deployed anything in JWS for ages - I'm the innocent end user

[trembovetski]

> Seems the priority is low, so I don't see that being fixed anytime soon.

It's not really that, it's just that I literally don't know how to improve this. As you can see from the bug report I'd tried a bunch of different approaches, without much success. If you have any ideas or know any d3d gurus, be my guest, the code was ported to jdk7 which is open sourced.

Dmitri

[EgonOlsen]

> Seems the priority is low, so I don't see that being fixed anytime soon.

It's not really that, it's just that I literally don't know how to improve this. As you can see from the bug report I'd tried a bunch of different approaches, without much success. If you have any ideas or know any d3d gurus, be my guest, the code was ported to jdk7 which is open sourced.

Dmitri

Just disable the pipeline for applets and let the user decide if he/she wants to use it in combination with the new plugin. If not that, disable it for the old plugin at least. The way it is now, i can disable it for the new plugin, but there's no way to do the same for the old plugin...which is the plugin running on the majority of systems ATM and especially on those that suffer from this problem: The some years  old AGP based machines with something like a GeForce 5x00, 6x00 or 7x00 in it.

[Mr. Gol]

btw, has anyone seen the new Nimbus look and feel's class names? The look and feel itself is very nice, a real step up from the horrible LAFs that have been the default for years. But the class names, come on:

com.sun.java.swing.plaf.nimbus.InternalFrameInternalFrameTitlePaneInternalFrameTitlePaneCloseButton WindowNotFocusedState

[trembovetski]

btw, has anyone seen the new Nimbus look and feel's class names? The look and feel itself is very nice, a real step up from the horrible LAFs that have been the default for years. But the class names, come on:

com.sun.java.swing.plaf.nimbus.InternalFrameInternalFrameTitlePaneInternalFrameTitlePaneCloseButton WindowNotFocusedState

Why do you care? These were automatically generated by the nimbus design tool, of course.

Dmitri

[trembovetski]

Just disable the pipeline for applets and let the user decide if he/she wants to use it in combination with the new plugin. If not that, disable it for the old plugin at least. The way it is now, i can disable it for the new plugin, but there's no way to do the same for the old plugin...which is the plugin running on the majority of systems ATM and especially on those that suffer from this problem: The some years  old AGP based machines with something like a GeForce 5x00, 6x00 or 7x00 in it.

How about you disable it for your applets? It's possible with the new plugin (since it can launch a new vm if you speficy a flag or property which is different from already running vms). You will only get the new plugin with 6u10 where the new pipeline is, and the new plugin is enabled by default on all browsers that you probably care..

Dmitri

[EgonOlsen]

How about you disable it for your applets? It's possible with the new plugin (since it can launch a new vm if you speficy a flag or property which is different from already running vms). You will only get the new plugin with 6u10 where the new pipeline is, ...

Well, i've already written that i can disable it myself with the new plugin and most likely, i have to. But i can't do that for the old plugin and that just plain sucks.

...and the new plugin is enabled by default on all browsers that you probably care..

No. I've some talkback function (can be disabled by the user of course) in my stuff and people have current VMs but they have old browsers and often enough hardware from the stone age. The new pipeline disabled by default for the old plugin...that's all i want for now...you are not promoting applets by killing performance for a lot of people with this new pipeline. Anyway, we already had this discussion IIRC...