In RTC, you can independently select configurations at the component
level (either by selecting arbitrary baselines, or by dropping/adding
change sets from the history of that component in your workspace).

At a finer granularity, you would change your configuration by
adding/removing change-sets (you can think of change-sets as
"fine-grained branches). One way to find change-sets to add/remove, is
to look at the history of a particular file ... that will give you a
list of change-sets that you can remove from your configuration. In the
history view, you can select "show all in repository", which tells you
what change-sets you can add to your configuration to modify the version
of that file.

Cheers,
Geoff

Thanks. Doing this at the granularty of components would be too large I think. I tried doing the change-set approach.

I went to a project in my workspace/sandbox, right - clicked on a package folder (meaning to get the info about history for all items in that package, together), and found that "history" was not an available pick. It's only an available pick on files. Is this how it is supposed to work? (Because in SVN, we're used to doing operations on arbitrary aggregations by clicking on folders...)

The granularity of 1 file is too small for our typical use cases. Is there a way to use folder hierarchies (e.g., all files in a Java package) in these kinds of operations?

-Marshall

On 5/5/2011 7:23 AM, marshallschor wrote:

Frequently, (in our current processes, working with SVN) we find it
useful to switch (parts of) a checked-out Eclipse Project to a
previous or more recent revision/branch/tag/trunk. There is an SVN
"switch" capability, which shows the revisions as well as
other branches/tags/trunk available, and allows switching that folder
(which could be a subfolder of the Eclipse project) to that other
version.

I see in RTC you can examine and compare other versions and baselines,
but I don't see how to look at other "branches" (e.g.,
versions from other streams) and don't see how to "load"
those into your active sandbox, so that you can try running with
pieces of other versions of code, etc. (useful for debugging).

Is this not supported/allowed?

-Marshall