When you regenerate profile tooling code, non-code files
such as plugin.xml and plugin.properties are overwritten. You can
customize preferences so that these files are not overwritten when
you regenerate the profile tooling.
About this task
To prevent the regeneration of non-code profile tooling files:
Procedure
- Right-click the profile tooling model; then click Properties,
click Tooling Model Generation, and click the General tab
of Tooling Model Generation.
- Using the menus in the Overwriting Files group, specify
one of the following preferences for each profile tooling file that
is listed:
- Overwrite: This option overwrites the
file completely.
- Ignore: This option skips the file
and does not overwrite it. If you select this option, you might encounter
significant problems if several changes were made to the profile or
the profile and tooling model.
- Ask: This option prompts you during
the tooling code generation to specify whether to overwrite the file
or keep it in the same state.
Tip: If your changes result in defective profile
tooling code, you can return the profile tooling plug-in to a working
state by selecting
Overwrite for each file;
then, you can regenerate the tooling code. In addition, you can create
a backup copy of each file that is specified to be overwritten. For
example, if you decide to overwrite the plugin.xml file, when you
re-generate the tooling code, the old plugin.xml file is time-stamped
and saved in your project. You can use these backup versions during
the development of your plug-in, and to compare older versions of
the files with the current version.
You can compare the current
version of the profile tooling files with older versions, even if
you do not create a backup copy through the Create backup
copy of overwritten files check box option. In the Project
Explorer view, right-click a specific file; then click to compare versions of the file. However, you might
choose to explicitly create backup copies because you can rename the
files for easier reference.