Changing baseline creation options

When you change the baseline creation options, you modify the template used for determining the product and project versions in the baseline and the date format used, if the date is part of the template.

Additionally, you can specify what character to use to replace illegal characters in the version. You can opt to always include all subprojects in the baseline, regardless of the release set for the subprojects.

The following procedure shows how to change the settings for these options, and preview the changes when you are Creating a baseline.

Procedure

  1. Start the Options dialog box by clicking Tools in the main menu and choosing Options.
  2. Click the Actions tab, then click Create Baseline in the left pane.
  3. Change the version template keywords.

    Change, remove, and add version template keywords by typing directly in the Version Template field. For example, change version template keywords so that new baselines have the build number in the name by default.

    Add new keywords by clicking Add Keyword icon.

  4. Change the date format keywords.

    Change, remove, and add date format keywords by typing directly in the Date Format field. You can add new keywords by clicking Add Keyword icon.

  5. Change the character used to replace illegal characters in the version.

    For example, if you enter %platform as part of a project version template, and the build management project has a platform of SPARC-solaris, the version string displays as SPARC_solaris.

    The following are illegal characters; do not enter them in this field: / \ ' " : ? * [ ] @ - # (and the current delimiter in use). To find out what the version delimiter is, see the version command (also available for Oracle and Informix®).To find out how to change the version delimiter, see the delimiter command.

  6. Set the Always include all subprojects regardless of release option so that the Create Baseline dialog box includes all subprojects, regardless of the release set, for any new baseline created.

    If you set this option, then all projects for a project hierarchy, regardless of the release value, are available. If you do not set this option, all prep subprojects and static subprojects with a component that matches that of the top-level project are used.

    This option is cleared by default.

  7. To return to the default settings after making changes, click Use Defaults.
  8. Click Apply or OK to save the changes.

Feedback