A quick question on component addition

Changing the ownership of component from an user to a project area will do the trick!

Thanks!

RTC 2.0 on Windows

If I add a component directly at the stream level I see that component in the "Components" folder (RTC Project -> Source Control -> Components). But if I add a component at the repository workspace level and deliver that component to a steam I don't see that component under the "Source Control-> Components" folder? Why is this?

Thanks!

Components are owned either by individual contributors or by the project
areas. When you add it directly to the stream, the owner of the component
is the owner of the stream. When you add it to a repository workspace,
the owner is the logged in user. You can log in as that user and find the
component under his "My Repository Workspaces -> Components" node. From
there, you can right-click the component and change the owner to the
appropriate project area.



On Fri, 07 Aug 2009 05:53:51 -0400, theju
<thejaswim> wrote:

RTC 2.0 on Windows

If I add a component directly at the stream level I see that component
in the "Components" folder (RTC Project -> Source Control
-> Components). But if I add a component at the repository
workspace level and deliver that component to a steam I don't see
that component under the "Source Control-> Components"
folder? Why is this?

Thanks!

--

It's important to distinguish the "ownership" of a component from
whether or not a particular component is "in the configuration" of
something.

What makes this a little confusing is that both relationships are shown
in the Team Artifacts explorer via nesting.

Happily, the kind of things that can "own" a component (a user or a
process area) are different from the kinds of things that can have a
component in their configuration (a workspace or a stream), so it
actually isn't ambiguous.

In particular, whenever you see a component under a "Components" node,
that indicates ownership. If the Components node is under a project
area, that means that the component is owned by some process area in
that project area. If the Components node is under the "My Workspaces"
node, then it is owned by the currently logged in user.

But when you see a component under a stream or a workspace node, that
means that component is "in the configuration" of that stream or workspace.

Note: A component is owned by exactly one thing, but is in the
configuration of an arbitrary number of things (0 or more), so a
component will always appear in at most one Components node (you won't
see it under any Component node if it is owned by a user that isn't
currently logged in), but can appear under an arbitrary number of stream
or workspace nodes.

Note: For the record, I believe it would have been clearer to have a "My
Components" node at the same level as "My Repository Workspaces" and "My
Team Areas", rather than a Components node nested under "My Repository
Workspaces", since this can mislead you into thinking that these
components are in the configuration of each of your workspaces. I've
submitted enhancement 89544 for this.

Cheers,
Geoff

theju wrote:

RTC 2.0 on Windows

If I add a component directly at the stream level I see that component
in the "Components" folder (RTC Project -> Source Control
-> Components). But if I add a component at the repository
workspace level and deliver that component to a steam I don't see
that component under the "Source Control-> Components"
folder? Why is this?

Thanks!