Refactoring Artifacts

Refactoring artifacts includes tasks such as moving an Artifact from one project to another, moving an artifact from a package to another, renaming artifacts, etc..

Usual Eclipse mechanisms for refactoring are leveraged within Tigerstripe to make all these operations intuitive. More specifically, let's review the following operations:

Moving Artifacts across Tigerstripe projects and/or packages
Renaming Artifacts

Moving Artifacts

First, make sure that the Tigerstripe Perspective is active.

In the Tigerstripe Explorer, you can drag and drop Artifacts from any location in a src package to any location in a target src directory. This will move the internal file used to store the artifact and adjust the package name as needed.

The same action can be obtained by a right-click on the Artifact in the Tigerstripe Explorer and selection of the Refactor->Move... menu entry.

In most cases, Tigerstripe is able to maintain references to the artifact being refactored. However, in some case this may not be possible. In this case, errors will be flagged by the Tigerstripe auditor so they can be fixed manually.

Renaming Artifacts

First, make sure that the Tigerstripe Perspective is active.

Select the artifact to rename in the Tigerstripe Explorer and right-click. Select the Refactor->Rename... menu entry. A dialog box will open for you to fill in the new name for that artifact.

In most cases, Tigerstripe is able to maintain references to the artifact being refactored. However, in some case this may not be possible. In this case, errors will be flagged by the Tigerstripe auditor so they can be fixed manually.