What's up with the automatic updater?
Isn't it supposed to figure out that a new version has been released or am I missing something here
It's been broken for a looooong time, apparently - Sun hasn't considered fixing it all that important
. Nah, I haven't actually checked the bug report, but when it happened to me that 1.4.2_03 was broken, several people told me this was a long-standing problem. At the very least, it doesn't detect _ updates.
Which is actually quite sensible.
What's mind-screwingly stupid is the decision to publish MAJOR updates in a "release that is not a release" and *refusing* to increment the version number. It's Sun's new versioning scheme - all versions of 1.5 will be 1.5.0 - just, 1.5.0_1 up to 1.5.0_25, etc </sarcasm>.
In all honesty, I think it's another of those "clever" ideas by Sun's marketing dept (responsible for so many own-goals over the years...). I reckon they're trying to "prove" to the world that:
1. Java is a mature platform
2. Sun knows what regression, unit, and system tests are
Since both have historically been kind of difficult to believe given track record (basic bugs STILL appear in the core libraries, like java.util, or Swing, that should have been detected by "obvious" unit tests...), this scheme of never updating the version number - making it look like there weren't any bugs to fix - pretends that both issues are resolved.