Configuration of Source Code Import Dialog

In the dialog, you configure which create templates are used by the source code import.

Purpose

In this dialog, you configure which create templates are used by the source code import.

Prerequisites

To be able to configure the create templates for the source code import, you require the Configure privilege.

Call

Select Import/Export>Import>Source Code>Configuration to open the Configuration of Source Code Import dialog.

In this dialog, you can change the configuration for the import of source code. The configuration is stored in a model-specific way in the user-specific directory $INOHOME.

Structure

The dialog consists of six tabs.

  • Generator

    Here, you can set which prefix a stereotype should have that is used if no specific stereotype is specified.

    You can select the stereotype for the library. The library is searched for existing types upon import; these are reused and undefined referenced classes and interface are also created.

    You can select the stereotype for primitive types. Existing primitive types of this stereotype are used in the model configuration for typing attributes and operation parameters

    Javadoc comments content can be stored in the specification text for the respective model element when importing Java source code. Enter the logical name of the specification text in the "Text for Javadoc" field to do this. Javadoc is supported for class, operation, attribute, interface, enumeration type and enumeration value element types.

  • Methods

    Here, depending on the visibility of the method, whether it is static, and whether it is a constructor, you can define which stereotype is used for this method.

  • Properties

    Here, depending on the visibility of the property, whether it is static, and whether it has an access operator, you can define which stereotype is used for this property.

  • Parameter

    Here, you can define which stereotype is used for default, in, return, and final parameters.

  • Miscellaneous Elements

    Here, you can define which stereotypes are used for classes, interfaces, and many other element types.

  • Target Package

    Here, you can use the stereotype to define which packages are offered as target packages in the wizard.