[SCM] - Creating a Component Set to be loaded together
Hi, I was trying to figure out if following scenario is possible and how
to achieve it with RTC. I have different reusable components (internally
they are Java projects). Some Components require other Components to
compile. So for example, reusable Component B, internally uses reusable
Component A.
Now, I have a developer who need reusable Component B, but he is not
aware about the existence of Component A. Is there a way to
automatically force the load of Component A, when a developer loads into
his workspace Component B?
I am looking for something similar to Project Set File concept used by
Eclipse with CVS: http://wiki.eclipse.org/PSF
Note: perhaps this concept can be "implemented" in a different way in
RTC not using Components, and I am in the bad track.
Thanks in advance,
Chemi.
to achieve it with RTC. I have different reusable components (internally
they are Java projects). Some Components require other Components to
compile. So for example, reusable Component B, internally uses reusable
Component A.
Now, I have a developer who need reusable Component B, but he is not
aware about the existence of Component A. Is there a way to
automatically force the load of Component A, when a developer loads into
his workspace Component B?
I am looking for something similar to Project Set File concept used by
Eclipse with CVS: http://wiki.eclipse.org/PSF
Note: perhaps this concept can be "implemented" in a different way in
RTC not using Components, and I am in the bad track.
Thanks in advance,
Chemi.
2 answers
Use a stream. Instead of telling the developer to load a component, tell them which stream has the configuration they need. As a team or project, your job is to keep a set of blessed streams configured so that it's easy for developers to get started, just point them at the stream they have to create a workspace from.
Project set files are external to the SCM system, so they are a lot harder to share.
Jean-Michel
Project set files are external to the SCM system, so they are a lot harder to share.
Jean-Michel
jlemieux wrote:
Ok, understood. So here the philosophy is: create and setup a stream,
instead of a PSF. What is more, using Follow-up actions, perhaps the
load can be done automatically when a developer gets into a team. Correct?
Thanks a lot,
Chemi.
Use a stream. Instead of telling the developer to load a component,
tell them which stream has the configuration they need. As a team or
project, your job is to keep a set of blessed streams configured so
that it's easy for developers to get started, just point them at the
stream they have to create a workspace from.
Project set files are external to the SCM system, so they are a lot
harder to share.
Jean-Michel
Ok, understood. So here the philosophy is: create and setup a stream,
instead of a PSF. What is more, using Follow-up actions, perhaps the
load can be done automatically when a developer gets into a team. Correct?
Thanks a lot,
Chemi.