Hello defaria,

you can remove componets by opening the editor for the stream (open the stream).
The select the components you don't want and remove them using the remove
button to the right.

Ralph

In playing around with RTC and Jazz I created a number of components
with names like "New Workspace Default Component" and
"New Workspace2 Default Component". I see this in the
Eclipse client under Team Artifacts: My Repository Workspaces:
Components. AFAICT there doesn't seem to be a way to delete such
components (no delete in right click menu). How does one delete such
nonsense?

Hello defaria,

Andrew Hoo ansered yur question.
I missed your point- there are also components within streams. So ignore
my comment.

Ralph

rschoonwrote:

Hello defaria,

you can remove componets by opening the editor for the stream (open

the stream).

The select the components you don't want and remove them using the

remove

button to the right.

I don't understand. Where is "the editor for the stream"? In
the Team Artifacts view I have my "project" listed - let's
call it foo. Under that I do have a Source Control and under that I
have both Components and "Team 1 Stream (Development)".
Under each of these I have "Default Component" and
"Default Component (1: Initial Baseline)". That's not the
problem.
The problem is at the top level of Team Artifacts I have My Repository
Workspaces which has Components under that. Then I have the follwoing

Foo (Public)
Foo (Public)
Foo (Public)
Foo Default Component (Public)
Foo Default Component (Public
New Workspace Default Component (Public)
New Workspace Default Component (Public)
New Workspace2 Default Component (Public)
It is these that I'm trying to get rid of.

Ralph's suggestion of using the Stream/Workspace editor is refering to
removing components from streams and workspaces for the purposes of
flowing changes with source control, but I think you mean from the Team
Artifact view of components that you own (because they were created by
default but you have no use for them).

You cannot delete them but you can change their ownership to a different
project area. It would then appear under the "Project Area/Source
Control/Components" for that project area. That would get it out of
<i>your</i> Team Artifacts View. To further hide it (from pickers, etc),
you could remove the &quot;Read Access&quot; control for that project area. Then
disconnect from this project area to get out out of sight and out of mind.



On Tue, 23 Jun 2009 01:37:52 -0400, defaria
&lt;Andrew&gt; wrote:

In playing around with RTC and Jazz I created a number of components
with names like &quot;New Workspace Default Component&quot; and
&quot;New Workspace2 Default Component&quot;. I see this in the
Eclipse client under Team Artifacts: My Repository Workspaces:
Components. AFAICT there doesn't seem to be a way to delete such
components (no delete in right click menu). How does one delete such
nonsense?

--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Sure thing if you made some on your own. I was thinking of the case where
you make a new Repository Workspace without flowing to a stream. It will
create a new component by default. Point being you somehow got components
and now you don't want them.

By the way, There are articles about source control at
http://jazz.net/library/article/41 that may help you understand while
you're learning.

Currently, being able to delete components is a special case. Components
in a production system will have more significant presence 'everywhere'.
That is, they will be present in many peoples workspaces and streams, they
will be governed by process, they contain change sets, they are tagged
with baselines... If you were able to delete a component, then you would
need a mechanism to deal with every dangling reference where they are
used. Restricting read/write access can effectively cut off a component
from the world without losing their history (yeah SCM!)

The issue about (not) being able to delete things does come up every now
and then, but I personally don't know where it is in the grand scheme of
things of RTC.

After you move ownership of the component to a Project Area, the yellow
man icon will disappear from the component and it will no longer appear
under your &quot;My Repository Workspaces: Components&quot;. It will be moved to
&quot;/Source Control/Components&quot;.

Note that you will need the process permission on that project area to
give it the ownership of the component.

Excuse the Opera signature. I use the Opera browser to read the newsgroup
and that was just the default signature.



On Tue, 23 Jun 2009 10:38:01 -0400, defaria
&lt;Andrew&gt; wrote:

Andrew Hoowrote:
Ralph's suggestion of using the Stream/Workspace editor is refering
to
removing components from streams and workspaces for the purposes of

flowing changes with source control, but I think you mean from the
Team
Artifact view of components that you own (because they were created
by
default but you have no use for them).

Not quite that they were created by default but rather I created a few
of them on my own in attempting to understand how all this works. I'm
still struggling with that.

You cannot delete them but you can change their ownership to a
different project area.

Well that seems odd that you cannot delete things...

It would then appear under the &quot;Project Area/Source
Control/Components&quot; for that project area. That would get it
out of
your Team Artifacts View. To further hide it (from pickers,
etc),
you could remove the &quot;Read Access&quot; control for that
project area. Then
disconnect from this project area to get out out of sight and out of
mind.

They appear under My Repository Workspaces: Components.

Using Opera's revolutionary e-mail client:
http://www.opera.com/mail/

Why you advertising here?

Andrew's explanation of why most objects in RTC cannot be deleted is
correct. For objects shared in many ways (often unknown to a given
user), it is safer to &quot;hide&quot; those objects than to delete them (having
objects you don't care about appear is an annoyance ... having objects
you do care about deleted out from underneath you is a disaster).

The main exceptions are objects that are very large or that are created
in large numbers by automated processes such as &quot;builds results&quot;. (Note
that build results can be deleted in RTC).

But I agree that RTC should at least make it easy for a user to
&quot;logically delete&quot; any object they want, rather than requiring that they
figure out how to rename, change ownership, and archive to achieve that
effect. I've submitted work item 86537 for that.

Cheers,
Geoff


defaria wrote:

Andrew Hoowrote:
By the way, There are articles about source control at
http://jazz.net/library/article/41 that may help you understand while

you're learning.

Interesting reading. I'll have to go through that sometime...

Currently, being able to delete components is a special case.
Components in a production system will have more significant
presence 'everywhere'. That is, they will be present in many peoples
workspaces and streams, they will be governed by process, they
contain change sets, they are tagged with baselines... If you were
able to delete a component, then you would need a mechanism to deal
with every dangling reference where they are used. Restricting
read/write access can effectively cut off a component from the world
without losing their history (yeah SCM!)

You're making the assumption that they were not created by accident
and that the user does not want to really delete them. Bad
assumption. While it makes sense in the case of production there can
still be instances where the end user just doesn't want that object
anymore. You can protect them from accidentally removing such things
but you should allow the administrator to delete them assuming they
know the risks and still decide that it's worth it to remove it. Such
is the case in my case. The components I created were created in
error. Why should I have to carry around that baggage if I don't want
to?

The issue about (not) being able to delete things does come up every
now and then, but I personally don't know where it is in the grand
scheme of things of RTC.

You should never cause a user to be stuck with objects that they
cannot delete. There are situations where deletion of such objects is
OK. My case is one of them.

After you move ownership of the component to a Project Area, the
yellow man icon will disappear from the component and it will no
longer appear under your &quot;My Repository Workspaces:
Components&quot;. It will be moved to &quot;/Source
Control/Components&quot;./Source
Control/Components&quot;.

I take this to mean I could move it to another Project and ignore it -
'cept I don't have another project. Yeah I could create one but again,
I should be able to delete a component that I created by mistake. It's
not being used by anyone else.

Excuse the Opera signature. I use the Opera browser to read the
newsgroup and that was just the default signature.

I'm not understanding. When I post I post from jazz.net. Are you using
a news reader? I'd prefer NNTP...

In any event, how about configuring the default signature to something
other than an ad? I know, sometimes some software/servers inject ads
but quite frankly I see way too many ads as it is. They don't
advertise my company - why should I advertise for them?