What exactly is a component
Is a component meant to be an individually buildable folder or set of
folders ?? Or is a component just a set of folders that represent a
logical piece but perhaps aren't useable on their own ?
This is probably a best-practice question. I have a large source tree
and wondering whether I can break it down sensibly into separate
components.. trouble is, many of the sub-folders in the tree need stuff
in another sub-folder to build.
Can components have a 'depends on' relatonship between them ?
Lots of questions, I know.
Cheers
folders ?? Or is a component just a set of folders that represent a
logical piece but perhaps aren't useable on their own ?
This is probably a best-practice question. I have a large source tree
and wondering whether I can break it down sensibly into separate
components.. trouble is, many of the sub-folders in the tree need stuff
in another sub-folder to build.
Can components have a 'depends on' relatonship between them ?
Lots of questions, I know.
Cheers
2 answers
Hi David,
As you said, there are many ways to slice things up. Components provide the mechanism to do this and we don't really have the definite guide for what files and folders should be in the same component. The rough guideline we've been using is that a component contains a logical set of features that are usualy built and shipped together. In Jazz itself, we have a component per jazz component (scm, work item, build, process, repo).
With a huge source tree, for example in Jazz we have roughly 30K files/folders in our integration stream, we have component which depend on others. We don't yet model the 'depend on' relationship between components and instead use streams to pre-build a configuration of components which makes sense and is consistent.
HTH,
Jean-Michel
As you said, there are many ways to slice things up. Components provide the mechanism to do this and we don't really have the definite guide for what files and folders should be in the same component. The rough guideline we've been using is that a component contains a logical set of features that are usualy built and shipped together. In Jazz itself, we have a component per jazz component (scm, work item, build, process, repo).
With a huge source tree, for example in Jazz we have roughly 30K files/folders in our integration stream, we have component which depend on others. We don't yet model the 'depend on' relationship between components and instead use streams to pre-build a configuration of components which makes sense and is consistent.
HTH,
Jean-Michel
Thanks
It helps to understand how you intended components to be used.
Cheers
jlemieux wrote:
It helps to understand how you intended components to be used.
Cheers
jlemieux wrote:
Hi David,
As you said, there are many ways to slice things up. Components
provide the mechanism to do this and we don't really have the
definite guide for what files and folders should be in the same
component. The rough guideline we've been using is that a component
contains a logical set of features that are usualy built and shipped
together. In Jazz itself, we have a component per jazz component
(scm, work item, build, process, repo).
With a huge source tree, for example in Jazz we have roughly 30K
files/folders in our integration stream, we have component which
depend on others. We don't yet model the 'depend on' relationship
between components and instead use streams to pre-build a
configuration of components which makes sense and is consistent.
HTH,
Jean-Michel