You must deploy a profile before you can apply it to
a model.
Releasing custom UML profiles
Releasing a custom UML profile ensures that you cannot make changes to a profile that adversely affect models that have the released profile applied to them. After you release a profile, you cannot delete or rename the stereotypes, stereotype attributes, classes, enumerations, or metaclass extensions of a released profile. You can only make changes that are compatible with the released version of your profile.
Packaging custom UML profiles
When you have finished authoring your custom UML profile and you are ready to make it available to others, you must deploy your profile. One way to deploy your custom UML profile is to create a plug-in and package your profile in the new plug-in. Then, modify the plugin.xml file to include an extension point to your profile. You can then install the profile plug-in and apply the profile to a model. You should define a pathmap to the profile. Package your custom UML profile if you want the profile to be listed as a deployed profile in the product. You may first want to release the profile to ensure that you cannot make changes to a profile that adversely affect models that have the released profile applied to them.
Localizing custom UML profiles
If you need to translate the display names of your profile
to different natural languages, you can generate a file that lists the
display names of the stereotypes, attributes, constraints, enumerations,
and classes in your profile. The generated file has .properties as
its file name extension.