It’s time for … Plan B

In my previous entry I described two plausible plans for moving forward with JDK 7:

Plan A: JDK 7 (as currently defined) Mid 2012
Plan B: JDK 7 (minus Lambda, Jigsaw, and part of Coin) Mid 2011
JDK 8 (Lambda, Jigsaw, the rest of Coin, ++) Late 2012

Thanks to everyone who responded to that entry, both directly and indirectly. The voluminous feedback was strongly—though not universally—in favor of Plan B. As of today that is the plan of record for JDK 7 and JDK 8.

I’ve updated the feature list to reflect this decision. A new milestone schedule will be posted shortly.

Comments:

What about JSR310?
Looks like Oracle doesn't care about outside contributions ... especially after that Google fiasco.

Posted by steve on September 20, 2010 at 05:53 PM PDT #

Just a question, why JSR 308 is not included in jdk7 anymore ?

Rémi

Posted by Rémi Forax on September 20, 2010 at 06:57 PM PDT #

Would it be possible, after JDK 7, to move to a date-driven release schedule, rather than a feature-driven schedule?

Posted by David Leppik on September 21, 2010 at 02:05 AM PDT #

Hello,

Thanks, this sounds like good news!

As the developer of a JVM-targeted compiler (and also
of a supporting class-file encoding/decoding library),
I would like to ask the following questions:
- it is safe to consider that the only modification of the
class file format for the upcoming JDK7 is the support
for "invokedynamic (ruling out extended annotations,
and modules)?
- is there any (even bare) indication of the date for
feature-freeze of the "java.dyn" package?

Kind regards,

x9c

Posted by x9c on September 21, 2010 at 02:44 AM PDT #

Will JSR-310 be included in JDK7 or 8?

Posted by Jason Porter on September 22, 2010 at 02:44 PM PDT #

That's awesome news. Plan B announced at JavaOne this year.

We'd still like to know more details about what will be in JDK7 and what will be in JDK8.

We're of course voting for our favorite RFE for dynamic code replacement. I was encouraged by Thomas Würthinger's talk at JavaOne, and the download available from him at http://ssw.jku.at/dcevm/publications/. Any thoughts on getting that into JDK7 or JDK8?

Posted by guest on September 23, 2010 at 10:16 AM PDT #

How long will JDK6's standard support continue after JDK7 ships?

Will JDK7 have three years of standard support? That's implied by: http://www.oracle.com/technetwork/java/javase/overview/faqs-jsp-136696.html#1q2

Posted by John Dallman on September 26, 2010 at 09:20 PM PDT #

First, I am happy Plan B has been choosen, since JDK 7 is awaited since a long time.

Secondly, while the JDK 7 roadmap, I think some minor changes could be still added to JDK 7.

Thirdly, as an example, I have thought about the following feature:
(a) make 'mutable' as a keyword
(b) define an compiler option so that when using this option, all variables/parameters would be 'final' by default
(c) enable to use the 'mutable' keyword to let a variable/parameter change if option (b) is used.

Well, I think this feature would improve Java advantages in the realm of multicore programming, that is, multi-threaded programming.
And it's more safe, just as stated here: http://javarizon.wordpress.com/2010/06/26/why-every-java-field-should-have-been-final-by-default/

Is there a web place where developers could post their (minor for next JDK 7, and not so minor for next JDK) suggestions to let evolve Java ?
Thanks.

Posted by Dominique De Vito on September 27, 2010 at 12:05 AM PDT #

Post a Comment:
Comments are closed for this entry.
About

This blog has moved to http://mreinhold.org/blog. <script>var p = window.location.pathname.split('/'); var n = p[p.length - 1].replace(/_/g,'-'); if (n != "301") window.location = "http://mreinhold.org/blog/" + n;</script>

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today
News

No bookmarks in folder

Blogroll

No bookmarks in folder

Feeds
RSS Atom