# Eclipse 3.2 Plug-in Migration FAQ

1. Legacy Action With No Label
2. Usage of IDs with dots (".") in Extension Points, Extensions, and Content Types

## Legacy Action With No Label

If you are using the action-based extension points, then you may want to specify either a `definitionId` or a non-empty `label`. If you don't do this, then in the "Uncategorized" category, there may be commands called "Legacy Action With No Label". They will appear in the keys preference page. A warning will be printed to the log.

In 3.2, all actions are converted into commands when parsing the registry. As such, actions without a definition id have a command generated for them. This command needs a label, which is typically drawn from the label on the action. In the case of actions appearing in the tool bar, sometimes neither a definition id nor a label were specified.

## Usage of IDs with dots (".") in Extension Points, Extensions, and Content Types

In the past, IDs specified for extension points, extensions, and content types were expected to be "simple IDs" with no dots in them (e.g., "myPoint", not "my.Point", not "myPlugin.myPoint"). This rule was specified, but not enforced.

In the release 3.2 we added processing of fully-qualified IDs (e.g., "org.eclipse.myPlugin.myPoint"). However, it turned out that some components had previously used IDs with dots and the change broke functionality provided by those components. To preserve backward compatibility for IDs of extension points and extensions, we added special processing based on the version of the XML file:

- If the XML file has the tag <?eclipse version="3.0"?>, the runtime functionality remains the same as before (plug-in ID is added to the simple name)
- If the XML file has the tag <?eclipse version="3.2"?>, the IDs with dots are treated as fully qualified names (no plug-in ID is added to the name).

Details can be found in the bug 128866.

We recommend switching to the 3.2 format as the usage of IDs with dots was never intended to be supported in the 3.0 format. (Simply put, there is no guarantee that it works in all cases today or that it will work the same tomorrow.)

This processing of the <?eclipse version> tag applies to IDs of extension points and extensions, but not to the IDs of content types (see bug 139491).