Creating and Editing Dependency Artifacts

As with any Tigerstripe Artifact, Dependency Artifacts can be created through a specific wizard and further edited with a form-based editor. This section covers all details and options available on Dependency Artifacts.

New Dependency Wizard

First, please make sure the Tigerstripe Perspective is active.

The New Dependency Artifact wizard allows the creation of new Dependency Artifacts within a Tigerstripe Project. The wizard can be open from either the button from the drop down Tigerstripe icon in the toolbar or from the Tigerstripe->New->Dependency entry in the top menubar. The following dialog will appear:

As with any other type of Tigerstripe Artifact wizard, the New Dependency Artifact wizard requires a set of parameters before the Dependency artifact can be successfully created.

Source Project: the source project in which the dependency artifact shall be created. In most cases, Tigerstripe is able to pre-populate this field based on the context. If not populated, or if the wrong project was selected, the Browse button can be used to select the correct Tigerstripe project in which the artifact shall be created.

Artifact Package: each artifact is created within the scope of a package. This field shall contain a valid package name. All non-valid names will be rejected and flagged by the wizard.

Artifact Name: a valid name for the artifact. This name uniquely identifies the artifact within the scope of its package. All non-valid artifact names will be rejected and flagged by the wizard.

aEnd Type: the fully qualified name of the artifact at the starting end of this association

zEnd Type: the fully qualified name of the artifact at the terminating end of this association.

Once all the required parameters are filled in, press the Finish button to create the corresponding Dependency artifact. Upon creation, a corresponding icon will appear in the Tigerstripe Explorer, and the main editor page will be set to the overview tab of the corresponding artifact editor. From this page, the dependency artifact can be further edited and additional information can be filled in.

Editing a Dependency Artifact

First, please make sure the Tigerstripe Perspective is active.

To edit an existing Entity Artifact, simply select its corresponding entry in the Tigerstripe Explorer, and double-click to open it in an editor. Entity Artifacts are made of the following details:

General Information: common to all Artifacts, the general information section covers high level information such as version, description.

Detail: dependency end details can be defined on this artifact.

Once you have edited your changes, make sure you Save your changes for them to be taken into account by Tigerstripe. To save, either select the Save option from the File menu entry in the menubar, use the save icon in the toolbar, or hit ctrl-s.
General Information

The General Information section contains the following information:

Project: the identifier of the Tigerstripe project where this artifact is defined, as it appears in the Tigerstripe Explorer view. This field cannot be edited. For information on how to move artifacts across projects in the workspace, please visit this section.

Package: the name of the package where the artifact is defined. This field cannot be edited. For more information on how to move artifacts across packages, please refer to this section.

Name: the name of the artifact. This field cannot be edited. For more information on how to rename artifacts, please refer to this section.

Description: a textual description of the artifact. This field can include any HTML code and should document the artifact. It is passed to the corresponding webpage when a project is published to website. For more details on Artifact documentation, please refer to this section.

Extends: the fully qualified name of the super-artifact (ie. the name of the artifact being extended by the current artifact). This is how inheritance is achieved between artifacts. For more information about inheritance within Tigerstripe models, please refer to this section.

Dependency End Details

To edit this depdendency's end details, refer to the Details section. The section looks as shown below:

Each end of the dependency can be further edited. You will find the following detail for each end:

Type: the fully qualified name of this end of the association