Would it be an alternative to create a repository workspace for the
common stream and another one for the stream_a? In that case he won't
see the outgoing new common component when delivering to stream_a.

A build workspace - if exists - could be setup by adding components from
both streams. What I do not know is, whether the build engine will be
capable to accept all incoming changes from stream_a and common_stream
at the same time, as the build workspace carries just one of them as
flow target.

On Wed, 09 Jul 2008 14:57:59 +0000, Tullio_Tancredi wrote:

what do you mean with "have
a scoped collaboration with that stream for that component"? Is it
related to creating scoped flow targets for the streams? If yes, how I
can do that?


Once you load your workspace, select the common component in the pending
changes view and run "Change flow target...", select the common stream.

- Dmitry

what do you mean with "have
a scoped collaboration with that stream for that component"? Is it
related to creating scoped flow targets for the streams? If yes, how I
can do that?

Hi all,
we are evaluating to use Jazz for developing next release of our
product. At the moment, I'm studying the Jazz source control in order
to port all our product source code on Jazz. Our product is a suite of
releases with several components. Some of these components are shared
with more releases.
My question is how is it possible to share a component with more
streams and assure that every changes to that component will be
available to each stream that includes it?

I made some tests by defining for examples the following two streams:
a) stream_a: common_component
b) stream_b: common_component + component_1 + component_2

where in the stream_b, the common_component has been added as a
component belonging to an other stream (stream_a).

I shared the common_project (it is the project contained in the
common_component) with the stream_a and all other projects (contained
into the component_1 + component_2) with the stream_b.

What I saw is that if I change some files in the common_component on
my repository workspace and deliver changes on the related stream
(stream_a), the repository files related to the common_component
contained into the stream_a are correctly updated while the
repository files related to the common_component contained into the
stream_b are not updated.

The problem is that in order to build the stream_b I need the last
version of code of all components (common_component + component_1 +
component_2).

Could someone help me in finding the right way to share source code /
components between different streams and so to make available changes
on common code to all streams that contain that components?

Thank very much in advance,

Tullio

The workflow that we currently support is as follows:

- deliver changes to stream_a
- change flow target to stream_b
- deliver changes to stream_b