Editing the Source Files of the Component 

To change a development component, you execute these steps:

·        Synchronizing a DC in the Local File System

·        Changing the file

·        Locally building and testing it

·        Checking in the changes (in the activity) into the repository

The development environment monitors the files that belong to a DC. If you change these files before checking them out, it asks you to assign the changes to an activity list. For more information, see Editing Development Components.

Besides the files that contain the source code or archive state, there are additional files that contain information about relationships to other DCs or about public parts. We call this information the component DC meta data. For information on how to edit this data, see Editing the Component Meta Data.

Editing the Source Files

...

       1.      To change the source files of a component, select the perspective that corresponds to the component type.

       2.      In the context menu of the component, choose one of these:

¡        DTR →Edit: Other users can also check out this file.

¡        DTR →Edit (Exclusive): The file is locked for other users until you check it back in.

An activity is created.

       3.      Make your changes.

       4.      Save your changes.

Locally Building the DC

Before you check in your changes to the DTR, you should compile (build, make) the DC on your machine. If a local test environment exists, test your changes now. Only if compilation goes through (and local testing is successful) you should check in your changes.

...

       1.      Open the perspective that belongs to the component type.

       2.      In the context menu of the DC to be built, choose Build.

A dialog box appears.

       3.      Check the selected action and the DCs concerned in the dialog window and make changes, if necessary.

The development environment automatically recognizes, which components have changed and need to be built, and marks them accordingly. However, you can always change these selections, for example, if you want to enforce the building of a component.

If errors occur during the DC build, you can view them in the General User Outputview.

Checking In Changes Into the Repository

After you made sure that your changes do not trigger compilation errors, check in your activity with the changes you made.

...

       1.      Switch to the Open Activities view (you can integrate this view in any perspective using the menu path Window → Show View →Other... → Design Time Repository → Open Activities).

       2.      In the context menu of the activity, choose Checkin.

 

The following distinction between active an inactive workspace only applies when a Component Build Service is used:

As the development takes place in the inactive workspace, your changes will become visible only for those who are using the same inactive workspace. This means that the developers working on the same DC (in the same compartment and configuration), see the changes directly after their release.