I believe it's "targetted for release this summer" (northern hemisphere). I believe I heard a june data bandied around somewhere, but that could just be wishful thinking.
Problem with that is, whenever it is released it will have almost no tool support. I've been using the generics prerelease with CodeGuide for sometime right now, and I'll tell you, NOTHING out there supports the JDK 1.5 syntactic sugar. Eclipse doesn't even have the features on the radar. There is a update or something for generics, et. al. in Eclipse but it doesn't work and isn't scheduled for the 3.x release cycle. Which means I'd guess, at least a year for support there. IDEA has partial support, but tends to be buggy or very incomplete from what I've heard. Anything, anything at all, that parses java source must be updated. So code-checkers, byte-code modifiers, etc. will need to be updated. It's a mess. I would not expect mainstream support for it, until all the tools catch up. Which will be a long time from now. So the real "release" of Java 1.5 could be 1+ years down the road.
The current idea EAP support should pretty complete from what I understand. It probably is buggy because it is an EAP after all but my understanding is that 4.1 was scheduled for May. More likely we'll be seeing something in June though.
Doug Lea said in late March that Beta 2 had slipped to end of May:
"This has been slipped to late May. This is very annoying to us in
JSR166. Besides the windows spin bug, the APIs in beta1 were from
before public review, and the longer they delay beta2, the more people
will need to adjust their code when the updated APIs appear. But
apparently other Tiger JSRs are enough behind that they needed to push
back schedules."
JSR-176 is the "Tiger" Feature List, which enumerates all the features that will make up JDK1.5, and includes a short description and rationale for each: http://www.jcp.org/en/jsr/detail?id=176
Actually Eclipse does have it on the radar and seem to be making good progress with it. They have a JDT effort code-named Cheetah that is has a lot of activity. It is not scheduled for the core 3.0 release for the very good reason that there is not a 1.5 release date they can plan to. Expect it officially available as a plugin for 3.0 pretty soon after the official 1.5.0 release.
that's the nice/nasty thing about writing your own blog server eh? (although I'm surprised Python doesn't have URI parsing built-in, maybe as David says it doesn't have legs after all :-)
appendix a has the full charset, appendix b has a useful URI parsing regexp
oh and BTW. your comment preview isn't really WYSIWYG as your CSS justifies the previewed text unlike the actual posted comment. Yeah, I know, tough crowd...
It's not that Python doesn't have URL parsing, it's that I am trying to rip the URLs out of the comment text with regexps. Thanks for the pointer to the regexp - I didn't make it all the way to appendix B.
I'm at JavaOne and they just said it would be out at the end of Septemer (2004). I'm using NetBeans to play with it but the syntax higglighting doesn't understand the new language features. I wasn't able to make Eclipse use the 1.5 compiler.
Comments
I believe it's "targetted for release this summer" (northern hemisphere). I believe I heard a june data bandied around somewhere, but that could just be wishful thinking.
Problem with that is, whenever it is released it will have almost no tool support. I've been using the generics prerelease with CodeGuide for sometime right now, and I'll tell you, NOTHING out there supports the JDK 1.5 syntactic sugar. Eclipse doesn't even have the features on the radar. There is a update or something for generics, et. al. in Eclipse but it doesn't work and isn't scheduled for the 3.x release cycle. Which means I'd guess, at least a year for support there. IDEA has partial support, but tends to be buggy or very incomplete from what I've heard. Anything, anything at all, that parses java source must be updated. So code-checkers, byte-code modifiers, etc. will need to be updated. It's a mess. I would not expect mainstream support for it, until all the tools catch up. Which will be a long time from now. So the real "release" of Java 1.5 could be 1+ years down the road.
The current idea EAP support should pretty complete from what I understand. It probably is buggy because it is an EAP after all but my understanding is that 4.1 was scheduled for May. More likely we'll be seeing something in June though.
Doug Lea said in late March that Beta 2 had slipped to end of May:
"This has been slipped to late May. This is very annoying to us in
JSR166. Besides the windows spin bug, the APIs in beta1 were from
before public review, and the longer they delay beta2, the more people
will need to adjust their code when the updated APIs appear. But
apparently other Tiger JSRs are enough behind that they needed to push
back schedules."
See http://article.gmane.org/gmane.comp.java.jsr.166-concurrency/856/
JSR-176 is the "Tiger" Feature List, which enumerates all the features that will make up JDK1.5, and includes a short description and rationale for each: http://www.jcp.org/en/jsr/detail?id=176
Actually Eclipse does have it on the radar and seem to be making good progress with it. They have a JDT effort code-named Cheetah that is has a lot of activity. It is not scheduled for the core 3.0 release for the very good reason that there is not a 1.5 release date they can plan to. Expect it officially available as a plugin for 3.0 pretty soon after the official 1.5.0 release.
The plan item (bugzilla) for 1.5 support is at:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=36938
(you need an Eclipse Bugzilla account, easy to get)
The download page for the early access "stable" release ;-) is at:
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-core-home/r3.0/main.html#updates
or you can get the latest greatest from the CVS if you are a cowboy ;-)
Alan, there appears to be a BUG in your URL parser. The above URLs are thought to be terminated by the underscore and hash characters...
Thanks for the info, Jed.
PS: That underscore problem is embarrasing: it won't even recognise a URL from this site! I think I'll fix it tonight.
that's the nice/nasty thing about writing your own blog server eh? (although I'm surprised Python doesn't have URI parsing built-in, maybe as David says it doesn't have legs after all :-)
http://www.ietf.org/rfc/rfc2396.txt
appendix a has the full charset, appendix b has a useful URI parsing regexp
oh and BTW. your comment preview isn't really WYSIWYG as your CSS justifies the previewed text unlike the actual posted comment. Yeah, I know, tough crowd...
Jed,
It's not that Python doesn't have URL parsing, it's that I am trying to rip the URLs out of the comment text with regexps. Thanks for the pointer to the regexp - I didn't make it all the way to appendix B.
a
I'm at JavaOne and they just said it would be out at the end of Septemer (2004). I'm using NetBeans to play with it but the syntax higglighting doesn't understand the new language features. I wasn't able to make Eclipse use the 1.5 compiler.
Eclipse 3.1M1 has failr good Generics support. Certainly enough support that I can happily develop 1.5 code with it.