It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,787

question asked: Mar 09 '12, 10:28 a.m.
question was seen: 4,985 times
last updated: Mar 09 '12, 10:28 a.m.

Related questions

FAQ - How this Forum works

Limit deliver conflict with replace component

0
Marco Delato (51●21●14) | asked Mar 09 '12, 10:28 a.m.
We have to implement a third party code scenario in which:
- on a certain Project Area (let's call it P) a given component (C1) is
developed
- on another Project Area (let's call it A) the component C1 is used but
cannot be modified
- on A, sometimes, C1 has to be replaced with a new version (baseline) from
P.

In ClearCase we had two UCM project A and P, both using C1; on A C1 is read
only, on P C1 is read-write.
To replace C1 in A we need only to rebase that component in A with a
baseline coming from P.

How to achieve this scenario in RTC 3?
We tried to use the pre-condition "Limit deliver.." in "Deliver (server)"
operation and set the permission as described in
https://jazz.net/library/article/215#componentadvisor but, if we try to
replace the component on the stream, we get the same error as we try to
deliver on that stream, even though the user's role allow the "Replace
Component" on that stream.

Why RTC doesn't allow the "Replace Component" operation on that stream?
Why RTC is not able to differentiate between "Replace Component" and
"Deliver" operations?

Thanks in advance,
Marco

2 answers

Most liked answers ↓|Newest answers|Oldest answers

0
permanent link
Marco Delato (51●21●14) | answered Mar 13 '12, 6:08 a.m.
You are right, I'm looking for the feature you described in wi 201067.

I think that feature is quite useful, expecially for project/users coming from ClearCase: in ClearCase you can define a read only component and you can rebase that component from another stream. Thus a component can be shared among several UCM projects, but can be modified only within that project in which it is read-write.

I think it is a very common scenario, isn't it?

I hope that feature will be included ASAP in RTC. In the meanwhile is there any workaround for solving that problem?

Cheers,
Marco
0
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered Mar 10 '12, 3:19 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
If you allowed "replace component", then effectively you are allowing an
arbitrary deliver (which is why that pre-condition does not distinguish
those two ways of updating the contents of a component).

I believe that what you are looking for is something like work item
201067, restricting flows to a stream to only be the declared flows.

Cheers,
Geoff


On 3/9/2012 11:26 AM, primeur.jazz.net wrote:
We have to implement a third party code scenario in which:
- on a certain Project Area (let's call it P) a given component (C1)
is
developed
- on another Project Area (let's call it A) the component C1 is used
but
cannot be modified
- on A, sometimes, C1 has to be replaced with a new version (baseline)
from
P.

In ClearCase we had two UCM project A and P, both using C1; on A C1 is
read
only, on P C1 is read-write.
To replace C1 in A we need only to rebase that component in A with a
baseline coming from P.

How to achieve this scenario in RTC 3?
We tried to use the pre-condition "Limit deliver.." in
"Deliver (server)"
operation and set the permission as described in
https://jazz.net/library/article/215#componentadvisor but, if we try
to
replace the component on the stream, we get the same error as we try
to
deliver on that stream, even though the user's role allow the
"Replace
Component" on that stream.

Why RTC doesn't allow the "Replace Component" operation on
that stream?
Why RTC is not able to differentiate between "Replace
Component" and
"Deliver" operations?

Thanks in advance,
Marco

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.