Adding custom file extensions to content builders

By default, the content builders run against files with the standard OpenEdge extensions (*.cls, *.i, *.p, and *.w). You can configure them to run against other files with custom extensions. For example, if you use .t as the file extension for your ABL trigger source code, you should add the .t extension to the list of extensions to ensure that the content builder runs against your trigger source code.

Choose Window > Preferences. The Preferences dialog appears.
Select Progress OpenEdge > Meta Catalog > Content Builders. The Content Builders page appears.
Select a content builder in the browse.
Choose Edit. The Edit Content Builder dialog appears.
Add your custom extension to the list in the Extensions field.
Choose OK.
Choose Apply to save your changes to the internal Meta Catalog definition file.

Note: The content builder definitions are also stored when you export catalog definitions to a file. Importing an existing definition file will overwrite any changes you made to the content builder definitions. If you do not want that to happen, you should export the catalog definitions again to overwrite the old file.