Skip navigation links


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: org.openide.util.enum > 1.20

Changes by affected class


Details of all changes by API and date

Old Enumeration API

enum package deprecated and replaced by Enumerations factory class

Jun 7 '04; API spec. version: 4.37; affected packages: org.openide.util.enum; made by: jtulach; issues: #41166
enum is a keyword in JDK 1.5 and as such it should not be used. That is the reason why we had to deprecated our org.openide.util.enum package. We are providing replacements of the original classes in form of factory methods org.openide.util.Enumerations.

Default filter enumeration accepts any non-null value

Oct 19 '00; affected top-level classes: FilterEnumeration
FilterEnumeration is no longer abstract. The default implementation accepts all non-null values.