Creating independent component

Hi,

since components only make sense in the SCM context, what would be the use case? What do you want to achieve?

Ralph

Can the components be created outsind Stream or Workspace? We have Source Control-> Components. If we right click Components,we don't see the option of creating components. IS it possible t ocreate components outsing streams or workspace?

thats true that Components make sense in SCM only, but if we don' want to make a component to flow with the stream immediately and keep it for later use,is it possible to create a component outside of workspace or stream...

Hi,

my approach would be to share the Eclipse projects in a new component in a private repository workspace. Please note, the component won't flow with a stream if you don't make the repository workspace flow with one. When sharing projects you have the option to create a repository workspace that does not flow with a stream essentially providing a backup.

The repository workspace can be read only for others and the component will be owned by the creator. You could later set a stream as flow target, deliver it to the stream and make the owner a team.

You could delete the repository workspace and the component would be still there. You could also change the owner of the component a team any time without requiring a repository workspace.

Ralph

thats true that Components make sense in SCM only, but if we don' want to make a component to flow with the stream immediately and keep it for later use,is it possible to create a component outside of workspace or stream...

Can the components be created outsind Stream or Workspace? We have Source Control-> Components. If we right click Components,we don't see the option of creating components. IS it possible t ocreate components outsing streams or workspace?

http://jazz.net/forums/viewtopic.php?t=10587

You may want to keep tabs on the topic you have already created asking about this.

Ralph's solution would seem to work for you. Create a workspace that does not flow with a stream. You still need to put a component in a workspace in order to put changes in it.

Also, adding a component to a workspace does not add the component to the flow target. You'll notice that the component is shown with a '+' decorator that indicates you are delivering a component addition but it is up to you to deliver it. Adding anything to the component keeps it to the workspace until you deliver to the workspace's flow target.