It's all about the answers!

Ask a question

Easy means for multiple streams to share a component and alw


Brian Gillan (3215330) | asked Feb 12 '09, 5:38 p.m.
We have a common component to be used across numerous features (over a
dozen) that are developed independently. So, we will have a stream for
each feature that contains a component for the feature itself, as well
as the common component. The desire is that the latest updates to the
common component are used and captured in a snapshot of the stream,
regardless of what stream it's updated in. Is there an easy way to
achieve this without having to manually flow changes between streams?
The only case where we might want the common component changes isolated
to the containing stream is for hot-fixes.

Brian

11 answers



permanent link
Jose Miguel Ordax Cassa (2.4k4126100) | answered May 13 '09, 1:31 p.m.
Geoffrey Clemm wrote:
Note that one advantage of Andrew's approach (having two workspaces)
over the approach I suggested (having one workspace with two flow
targets) is that you can see all pending changes with the default "show
only the current flows" behavior (with one workspace, you'd have to
select "show all flows").

Cheers,
Geoff

Another advantage I think, is that once you have loaded the code of the
common stream into your Eclipse local workspace, you won't be asked to
deliver that new code into the feature stream in the Pending Changes. Right?

Thanks for such interesting discussion thread. I think it could be the
source for a technical article in conjunction with the new authorization
scheme added in 2.0 to avoid unauthorized people to modify the common
component.

Regards,

Chemi.

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.