Note that you should not be representing a software component by an RTC
Project. You should be representing a software component by an RTC
component (and unless your software components are large, you'd probably
be storing multiple related software components in a single RTC component).

Cheers,
Geoff

On 2/21/2011 4:38 PM, khess wrote:

Assuming a software component is represented by an RTC Project, a
buildengine would have to be defined in every single software
component/RTC Project.

Is there a way to define a buildengine for the complete repository

What is an "oo build"?

Cheers,
Geoff

On 2/21/2011 4:38 PM, khess wrote:

Is there a recommended way to start a combined host/oo build? Our
environment is a hybrid of both.

In RTC, if you are using multiple components, you would use a "snapshot"
rather than a "baseline" to capture a configuration of your system. To
initialize a workspace with that snapshot, you can right click on that
snapshot in the RTC Eclipse GUI, and select the "New -> Repository
Workspace from Snapshot" operation.

Alternatively, if you want to update an existing workspace with that
snapshot, right click on that workspace in the Pending Changes view, and
select "Replace with -> Snapshot ..." and then select the desired
snapshot in the dialog box.

Cheers,
Geoff

On 2/21/2011 4:38 PM, khess wrote:

We currently generate a Clear Case dynamic view based upon a baseline
of a build (1 day ago, some months ago, whatever).

How can we manage this with RTC?

The format of the load rules file for a build is described in the
"Component Load Rules" page in the RTC on-line help.

Here's the example from that page:

# Two directives are supported:
# versionableName=
# RootFolderName=

# In this example the component contains the following tree of folders
# /MyMain/
# /MyMain/products/
# /MyMain/products/command line client/
# /MyMain/products/command line client/project1/
# /MyMain/products/command line client/project1/src/
# /MyMain/products/command line client/project1/src/A.java
# /MyMain/products/command line client/project1/src/... a number of
other sub directories and files
# /MyMain/products/command line client/project2/
# /MyMain/products/command line client/project3/
# /MyMain/products/MetroNome/project4/
# /MyMain/products/MetroNome/project4/build.script
# /MyMain/products/MetroNome/project5/
# /MyMain/products/RTC/project6/
# plus other directories under MyMain

# Entries starting with versionablename=
# provides the fully qualified name in the repository of the item to be
loaded
# If the item is a folder, it and all its children are loaded.
# This line loads the folder /MyMain/products/command line
client/project1/ and all the
# files and subfolders it contains
versionableName=/MyMain/products/command line client/project1/
# This line loads the file /MyMain/products/MetroNome/project4/build.script
versionableName=/MyMain/products/MetroNome/project4/build.script

# Entries starting with rootfoldername=
# Provides the fully qualified name in the repository of the folder
whose children are to be loaded
# The folder identified is not loaded, all the children of it are loaded.
# This line loads all the files and subfolders that the /MyMain/products
folder contains
RootFolderName=/MyMain/products/


Cheers,
Geoff

On 2/21/2011 4:38 PM, khess wrote:

How can we define load rules for a build? In a build definition we can
select a file where the load rules are specified.

What should this file look like?