When you create a new Eclipse plug-in project for Red Apps, you are required to add a Plug-in ID, version, plug-in name, and company name. These properties must conform to standards for Red Apps.

        IMPORTANT!    Whether you use Eclipse’s New Plug-in Project wizard, a Red App wizard, or a Red App sample plug-in, or convert an existing plug-in to a Red App, you are advised to review the project properties of your plug-ins to ensure compliance with Red App standards.

The New Plug-in Project and Overview screens in Eclipse have the fields that are described below. The Overview tab in the following figure is used to illustrate the plug-in project properties.

ID field.     The Plug-in Project ID must conform to these standards: Main and Dependent Plug-in IDs. Eclipse populates the BundleSymbolicName field in MANIFEST.MF with the value in the ID field.

Version field.     Eclipse displays a default version. Your plug-in version must conform to Main Red App and Dependent Plug-in Versions.

Name field.     The name is either the Red App name or a name of your choice for a dependent plug-in project. The name must conform to these standards:    Red App Names and Dependent Plug-in Names. The Red App name is displayed to end-users.

Provider field.     The name of the company or organization that is providing the Red App. This name conforms to Company (Provider) Names. The provider is displayed to end-users.

Activate This Plug-in when an Activator Class is Loaded: An Activator is a Java class that controls the life cycle of a plug-in. Select this option if it applies to your plug-in.

This plug-in is a singleton. All Red Apps are required to include the com.sabre.edge.redapp extension, therefore, they are singletons.