Java version history

From Wikipedia, the free encyclopedia

Jump to: navigation, search
Java Web Start, first introduced for J2SE 1.3, allows provision of applications over the Web by clicking a desktop icon or a link on a website.

The Java language has undergone several changes since JDK 1.0 as well as numerous additions of classes and packages to the standard library. Since J2SE 1.4, the evolution of the Java language has been governed by the Java Community Process (JCP), which uses Java Specification Requests (JSRs) to propose and specify additions and changes to the Java platform. The language is specified by the Java Language Specification (JLS); changes to the JLS are managed under JSR 901.

In addition to the language changes, much more dramatic changes have been made to the Java class library over the years, which has grown from a few hundred classes in JDK 1.0 to over three thousand in J2SE 5.0. Entire new APIs, such as Swing and Java2D, have been introduced, and many of the original JDK 1.0 classes and methods have been deprecated.

Some programs allow to convert Java programs from one version of the Java Platform to an older one (for example Java 5.0 backported to 1.4) (see Java backporting tools).

Contents

[edit] JDK 1.0 (January 23, 1996)

Codename Oak. Initial release[1]

[edit] JDK 1.1 (February 19, 1997)

Major additions included:[2]

[edit] J2SE 1.2 (December 8, 1998)

Codename Playground. This and subsequent releases through J2SE 5.0 were rebranded retrospectively Java 2 and the version name "J2SE" (Java 2 Platform, Standard Edition) replaced JDK to distinguish the base platform from J2EE (Java 2 Platform, Enterprise Edition) and J2ME (Java 2 Platform, Micro Edition). Major additions included:[3]

[edit] J2SE 1.3 (May 8, 2000)

Codename Kestrel. The most notable changes were:[4][5]

[edit] J2SE 1.4 (February 6, 2002)

Codename Merlin. This was the first release of the Java platform developed under the Java Community Process as JSR 59. Major changes included:[6][7]

[edit] J2SE 5.0 (September 30, 2004)

Codename Tiger. (Originally numbered 1.5, which is still used as the internal version number.[8]) Developed under JSR 176, Tiger added a number of significant new language features:[9][10]

  • Generics: Provides compile-time (static) type safety for collections and eliminates the need for most typecasts (type conversion). (Specified by JSR 14.)
  • Metadata: Also called annotations; allows language constructs such as classes and methods to be tagged with additional data, which can then be processed by metadata-aware utilities. (Specified by JSR 175.)
  • Autoboxing/unboxing: Automatic conversions between primitive types (such as int) and primitive wrapper classes (such as Integer). (Specified by JSR 201.)
  • Enumerations: The enum keyword creates a typesafe, ordered list of values (such as Day.MONDAY, Day.TUESDAY, etc.). Previously this could only be achieved by non-typesafe constant integers or manually constructed classes (typesafe enum pattern). (Specified by JSR 201.)
  • Swing: New skinnable look and feel, called synth.
  • Varargs: The last parameter of a method can now be declared using a type name followed by three dots (e.g. void drawtext(String... lines)). In the calling code any number of parameters of that type can be used and they are then placed in an array to be passed to the method, or alternatively the calling code can pass an array of that type.
  • Enhanced for each loop: The for loop syntax is extended with special syntax for iterating over each member of either an array or any Iterable, such as the standard Collection classes, using a construct of the form:
void displayWidgets (Iterable<Widget> widgets) {
    for (Widget w: widgets) {
        w.display();
    }
}

This example iterates over the Iterable object widgets, assigning each of its items in turn to the variable w, and then calling the Widget method display() for each item. (Specified by JSR 201.)

  • Fix the previously broken semantics of the Java Memory Model, which defines how threads interact through memory.
  • Automatic stub generation for RMI objects.
  • static imports
  • 1.5.0_17 (5u17) is the last release of Java to officially support the Microsoft Windows 9x line (Windows 95, Windows 98, Windows ME). [1] Unofficially, Java SE 6 Update 7 (1.6.0.7) is the last version of Java to be shown working on this family of operating systems. [2]
  • The concurrency utilities in package java.util.concurrent.[11]

J2SE 5.0 entered its end-of-life on 2008 April 8 and will be unsupported by Sun as of 2009 October 30.[12]

[edit] Java SE 6 (December 11, 2006)

Codename Mustang. As of this version, Sun replaced the name "J2SE" with Java SE and dropped the ".0" from the version number.[13] Internal numbering for developers remains 1.6.0.[14] This version was developed under JSR 270.

During the development phase, new builds including enhancements and bug fixes were released approximately weekly. Beta versions were released in February and June 2006, leading up to a final release that occurred on December 11, 2006. The current revision is Update 13 which was released in March 2009.

Major changes included in this version:[15][16]

  • Support for older Win9x versions dropped. Unofficially Java 6 Update 7 is the last release of Java shown to work on these versions of Windows. This is believed to be due to the major changes in Update 10.
  • Scripting Language Support (JSR 223): Generic API for tight integration with scripting languages, and built-in Mozilla Javascript Rhino integration
  • Dramatic performance improvements for the core platform[17][18], and Swing.
  • Improved Web Service support through JAX-WS (JSR 224)
  • JDBC 4.0 support (JSR 221).
  • Java Compiler API (JSR 199): an API allowing a Java program to select and invoke a Java Compiler programmatically.
  • Upgrade of JAXB to version 2.0: Including integration of a StAX parser.
  • Support for pluggable annotations (JSR 269).
  • Many GUI improvements, such as integration of SwingWorker in the API, table sorting and filtering, and true Swing double-buffering (eliminating the gray-area effect).

[edit] Java SE 6 Update 10

Java SE 6 Update 10 (previously known as Java SE 6 Update N), while it does not change any public API, is meant as a major enhancement in terms of end-user usability. The release version is currently available for download.[19]

Major changes for this update include:[19][20]

  • Java Deployment Toolkit, a set of JavaScript functions to ease the deployment of applets and Java Web Start applications.[21]
  • Java Kernel, a small installer including only the most commonly used JRE classes. Other packages are downloaded when needed.
  • Enhanced updater.
  • Enhanced versioning and pack200 support: server-side support is no longer required.[22]
  • Java Quick Starter, to improve cold start-up time.
  • Improved performance of Java2D graphics primitives on Windows, using Direct3D and hardware acceleration.
  • A new Swing look and feel called Nimbus and based on synth.[23]
  • Next-Generation Java Plug-In: applets now run in a separate process and support many features of Web Start applications.[24]

[edit] Current Version

Java SE 6 Update 13 (6u13) as of March 23, 2009.[3][4]

This release includes the highly anticipated 64-bit Java Plug-In (for 64-bit browsers only), Windows Server 2008 support, and performance improvements of Java and JavaFX applications. Learn more..."

[edit] Java SE 7

Codename Dolphin.[25] This is in the planning and development stages[26]. The Dolphin Project began in August 2006 and is tentatively scheduled for release in 2010.[27] New builds including enhancements and bug fixes are released approximately weekly.

New features that may be integrated in Java 7[28] include:

  • JVM support for dynamic languages, following the prototyping work currently done on the Multi Language Virtual Machine,
  • A new library for parallel computing on Multi-core processors,[29]
  • Superpackages (JSR 294), which are a way to define explicitly in a library or module which classes will be visible from outside of the library,[30]
  • Swing Application Framework, an infrastructure common to most desktop applications, making Swing applications easier to create.
  • Replacing the existing concurrent low-pause garbage collector (also called CMS or Concurrent Mark-Sweep collector) by a new collector called G1 (or Garbage First) to ensure consistent pauses over time,[31][32]
  • Various small language changes, grouped in a project called Project Coin.[33][34] These changes are still evaluated but could include: Strings in switch, more concise calls to constructors with type parameters, or multi-catch in exceptions.[35]

Also, there is an ongoing debate in the Java community on whether it would be appropriate to add built-in support for closures, a feature available in a number of other languages.[36][37]

[edit] References

  1. ^ Version 1.0 press release, Sun.
  2. ^ Version 1.1 press release, Sun.
  3. ^ Version 1.2 press release, Sun.
  4. ^ Version 1.3 press release, Sun.
  5. ^ Version 1.3 full list of changes, Sun.
  6. ^ Version 1.4 press release.
  7. ^ Version full 1.4 list of changes.
  8. ^ Version 5 release notes, Sun.
  9. ^ Version 1.5 press release.
  10. ^ Version 1.5 full list of changes.
  11. ^ Goetz, Brian (2006). Java Concurrency in Practice. Addison-Wesley. p. xvii. ISBN 0-321-34960-1. 
  12. ^ Java SE Downloads - Previous Release - JDK 5
  13. ^ Java brand naming.
  14. ^ Version 6, Java webnotes, Sun.
  15. ^ Version 1.6 press release.
  16. ^ Version 1.6 full list of changes.
  17. ^ Java Lobby.
  18. ^ Mustang’s HotSpot, Sun weblogs.
  19. ^ a b Java SE 6 Update 10 Overview
  20. ^ Introducing Java SE 6 Update 10
  21. ^ Java Deployment Toolkit
  22. ^ Version Download and Pack200 Support
  23. ^ Nimbus
  24. ^ Release Notes for the Next-Generation Java Plug-In Technology
  25. ^ JDK7, Sun.
  26. ^ Flanagan, David (2007-09-08). "The Open Road: Looking Ahead to Java 7". http://today.java.net/pub/a/today/2007/08/09/looking-ahead-to-java-7.html. Retrieved on 2008-03-09. 
  27. ^ What to expect in Java SE 7
  28. ^ Miller, Alex. "Java 7". http://tech.puredanger.com/java7. Retrieved on 2008-05-30. 
  29. ^ Goetz, Brian (2008-03-04). "Java theory and practice: Stick a fork in it, Part 2". http://www.ibm.com/developerworks/java/library/j-jtp03048.html?ca. Retrieved on 2008-03-09. 
  30. ^ Rusty Harold, Elliotte (2008-03-06). "The Open Road: Superpackages". http://today.java.net/pub/a/today/2008/03/06/jsr-294-superpackages.html. Retrieved on 2008-03-09. 
  31. ^ Humble, Charles (2008-05-13). "JavaOne: Garbage First". infoq.com. http://www.infoq.com/news/2008/05/g1. Retrieved on 2008-09-07. 
  32. ^ Coward, Dany (2008-11-12). "Java VM: Trying a new Garbage Collector for JDK 7". http://blogs.sun.com/theplanetarium/entry/java_vm_trying_a_new. Retrieved on 2008-11-15. 
  33. ^ "Project Coin". Sun Microsystems. http://www.openjdk.org/projects/coin/. Retrieved on 2009-03-30. 
  34. ^ Darcy, Joseph D. (2009-01-27). "Project Coin: Small Language Change Proposal Form Available". http://blogs.sun.com/darcy/entry/project_coin. Retrieved on 2009-03-30. 
  35. ^ Darcy, Joseph D. (2009-03-24). "Project Coin: For further consideration...". http://blogs.sun.com/darcy/date/20090324. Retrieved on 2009-03-30. 
  36. ^ Gafter, Neal (2006-08-18). "Closures for Java". http://gafter.blogspot.com/2006/08/closures-for-java.html. Retrieved on 2008-03-09. 
  37. ^ Gosling, James (2008-01-31). "Closures". http://blogs.sun.com/jag/entry/closures. Retrieved on 2008-03-09. 

[edit] External links

Personal tools