Overview (Java Platform UI)

Java Platform UI
Package	Description
org.netbeans.api.java.platform
org.netbeans.spi.java.platform	Registration of Java platform types.

JavaPlatformUI The Java Platform API permits access to installed Java platforms (for example, the J2SE JDK, or various mobile-device emulators for J2ME). Particular platform types are registered by modules and can store customized information about the platform to disk.
Note that this module concentrates the UI part of API. Its desktop-independent counterpart is in the org.netbeans.modules.java.platform module.

What is New (see all changes)?

May 14 '14 Desktop dependent java platform UI extracted

The following classes were moved into the org.netbeans.java.platform.ui module:
Please also see API changes of the original java.platform module.

Use Cases

The API can be used by any code wishing to know the list of installed platforms and information about each one; typically this would be used by project type providers to implement a customizer dialog. The SPI is intended to be implemented by a few modules supply support for locating and introspecting installed platforms, for example a JDK setup wizard.

Exported Interfaces

This table lists all of the module exported APIs with defined stability classifications. It is generated based on answers to questions about the architecture of the module. Read them all...

Group of java interfaces

Interface Name

In/Out

Stability

Specified in What Document?

JavaPlatformUI

Exported

Official

The Java Platform API permits access to installed Java platforms (for example, the J2SE JDK, or various mobile-device emulators for J2ME). Particular platform types are registered by modules and can store customized information about the platform to disk.
Note that this module concentrates the UI part of API. Its desktop-independent counterpart is in the org.netbeans.modules.java.platform module.

Implementation Details

What do other modules need to do to declare a dependency on this one, in addition to or instead of a plain module dependency?

Nothing.

Read more about the implementation in the answers to architecture questions.