Adding a single file to a SCM Component

Having a single file be the root of a component would mean that the
component could never contain more than that single file (which is why
it isn't supported). Why would you want to do that?

Cheers,
Geoff

Chemi wrote:

As in Eclipse, it is mandatory to have a Project as first unit in a
workspace structure, I don't know how to share a single file as root of
a component, I mean, without having it into a folder.

Should I use SCM CLI outside Eclipse? Can you share a simple sample?

And later to use it? I understand I should load it into an existing
folder/project in Eclipse. Right?

Thanks in advance,

Chemi.

Geoffrey Clemm wrote:

Having a single file be the root of a component would mean that the
component could never contain more than that single file (which is why
it isn't supported). Why would you want to do that?

Cheers,
Geoff

Well, I am studying a Clear Case to RTC migration and in this scenario
the user has in Clear Case several components defined where there isn't
a "parent" folder with the content but just a couple of documentation
files directly in the root of the component.

I understood that sharing such files directly from Eclipse (because
Eclipse workspace restrictions) was not possible but I thought it was
possible using SCM CLI interface.

So, if I understand you correctly it is not supported to have files in a
component in a flat way, it is mandatory to "encapsulate" them in a
folder. Is this correct?

Thanks in advance,

Chemi.

Chemi,

I think there is some confusion over terminology here. The root of a
component is always a folder. In RTC 1.0.x, this component root could
only contain folders, which we refer to as top-level folders. I believe
you are talking about having files at the top-level (i.e. as a child of
the component root). This is supported in RTC 2.0.

The easiest way to add a file at the top-level of a component is to load
the component root as a folder (see
http://jazz.net/library/article/192#LoadComponentRoot for a description
of how to do this). You can then add a file in this folder and check-in
and deliver the file as desired. Once he file is added, it can be loaded
directly, as described at http://jazz.net/library/article/192#LoadFile.

Hope this helps,
Michael

Chemi wrote:

Geoffrey Clemm wrote:
Having a single file be the root of a component would mean that the
component could never contain more than that single file (which is why
it isn't supported). Why would you want to do that?

Cheers,
Geoff

Well, I am studying a Clear Case to RTC migration and in this scenario
the user has in Clear Case several components defined where there isn't
a "parent" folder with the content but just a couple of documentation
files directly in the root of the component.

I understood that sharing such files directly from Eclipse (because
Eclipse workspace restrictions) was not possible but I thought it was
possible using SCM CLI interface.

So, if I understand you correctly it is not supported to have files in a
component in a flat way, it is mandatory to "encapsulate" them in a
folder. Is this correct?

Thanks in advance,

Chemi.

Michael Valenta wrote:

Chemi,

I think there is some confusion over terminology here. The root of a
component is always a folder. In RTC 1.0.x, this component root could
only contain folders, which we refer to as top-level folders. I believe
you are talking about having files at the top-level (i.e. as a child of
the component root). This is supported in RTC 2.0.

The easiest way to add a file at the top-level of a component is to load
the component root as a folder (see
http://jazz.net/library/article/192#LoadComponentRoot for a description
of how to do this). You can then add a file in this folder and check-in
and deliver the file as desired. Once he file is added, it can be loaded
directly, as described at http://jazz.net/library/article/192#LoadFile.

Hope this helps,
Michael

Thanks a lot. That was exactly what I was looking for. I read another
thread in this forum titled: "adding files to SC, which are not in
Eclipse project folders" which was related to the same concept but I
didn't understand it so clearly.

Thanks,

Chemi.