Introduction

What do the Dates Mean?

The supplied dates indicate when the API change was made, on the CVS trunk. From this you can generally tell whether the change should be present in a given build or not; for trunk builds, simply whether it was made before or after the change; for builds on a stabilization branch, whether the branch was made before or after the given date. In some cases corresponding API changes have been made both in the trunk and in an in-progress stabilization branch, if they were needed for a bug fix; this ought to be marked in this list.


Index of APIs

Incompatible changes by date

Fuller descriptions of all changes can be found below (follow links).

Not all deprecations are listed here, assuming that the deprecated APIs continue to essentially work. For a full deprecation list, please consult the Javadoc.

All changes by date

Changes by version

These API specification versions may be used to indicate that a module requires a certain API feature in order to function. For example, if you see here a feature you need which is labelled 1.20, your manifest should contain in its main attributes the line:

OpenIDE-Module-Module-Dependencies: $codebase > 1.20

Changes by affected class

org.netbeans.swing.plaf.Startup


Details of all changes by API and date


Look And Feel Customization

It is now possible to customize application-specific UIManager keys and values.

Jun 30 '11; API spec. version: 1.22; affected top-level classes: Startup; made by: saubrecht

Read more about the look and feel Customs branding property.

It is now possible to brand name of Look And Feel

May 6 '10; API spec. version: 1.16; affected top-level classes: Startup; made by: jtulach

Read more about the Look And Feel branding property.


Built on May 25 2012.  |  Portions Copyright 1997-2012 Oracle. All rights reserved.