It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,837

question asked: Feb 05 '08, 5:38 p.m.
question was seen: 5,485 times
last updated: Feb 05 '08, 5:38 p.m.

Related questions

Jazz SCM equivalent to CVS modules

0
Tom Frauenhofer (1.3k●5●84●35) | asked Feb 05 '08, 5:38 p.m.
Hi there

Using CVS over the years I've noticed that my team and others, often use
a CVS 'module' definition to work with a subset of a given CVS project.

For example, my team does porting work for a large existing product. We
load the entire product source tree (> 1.2Gig) into CVS. Throughout the
development project, we need to work with a much smaller (fixed) subset
(say only 300MB) of that tree. We define a CVS 'module' that includes
only the portion of the source that needs to be worked on so that
developers need not checkout gigabytes of data that they mostly never use.

After that long-winded description ...

1) is there any equivalent feature in the Jazz SCM

and if not

2) do teams using the Jazz SCM ever face this need see a 'subset' view
of their code ?

Cheers
Dave

4 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered Feb 05 '08, 9:18 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
You would use a Jazz SCM "component" to partition your source tree into
separate pieces.

Cheers,
Geoff (ClearCase Connector team)

David Ward wrote:
Hi there

Using CVS over the years I've noticed that my team and others, often use
a CVS 'module' definition to work with a subset of a given CVS project.

For example, my team does porting work for a large existing product. We
load the entire product source tree (> 1.2Gig) into CVS. Throughout the
development project, we need to work with a much smaller (fixed) subset
(say only 300MB) of that tree. We define a CVS 'module' that includes
only the portion of the source that needs to be worked on so that
developers need not checkout gigabytes of data that they mostly never use.

After that long-winded description ...

1) is there any equivalent feature in the Jazz SCM

and if not

2) do teams using the Jazz SCM ever face this need see a 'subset' view
of their code ?
0
permanent link
Evan Hughes (2.4k●13●18) | answered Feb 06 '08, 9:12 a.m.
JAZZ DEVELOPER
As Geoff says, components are the way to go. But our granularity doesn't stop there. When you're loading a component, you can choose which root folders should be copied to your local disk.

e
(Source Control)
0
permanent link
Jean-Michel Lemieux (2.5k●1●1) | answered Feb 06 '08, 10:18 a.m.
JAZZ DEVELOPER
As Geoff said, components are the first level of decomposition, but in
reality many projects already have a directory structure that they don't
want to split or refactor. There are a couple of things happening to
support finer grain loading that are being discussed in

https://jazz.net/jazz/web/projects/Jazz%20Project#action=com.ibm.team.workitem.viewWorkItem&id=42933

At a minimum we will support loading at any folder level for 1.0, a P2
is to remember this as you can with CVS modules or SVN externals.

Hope this helps.
Jean-Michel
Jazz Source Control Team

David Ward wrote:
Hi there

Using CVS over the years I've noticed that my team and others, often use
a CVS 'module' definition to work with a subset of a given CVS project.

For example, my team does porting work for a large existing product. We
load the entire product source tree (> 1.2Gig) into CVS. Throughout the
development project, we need to work with a much smaller (fixed) subset
(say only 300MB) of that tree. We define a CVS 'module' that includes
only the portion of the source that needs to be worked on so that
developers need not checkout gigabytes of data that they mostly never use.

After that long-winded description ...

1) is there any equivalent feature in the Jazz SCM

and if not

2) do teams using the Jazz SCM ever face this need see a 'subset' view
of their code ?

Cheers
Dave
0
permanent link
Tom Frauenhofer (1.3k●5●84●35) | answered Feb 07 '08, 12:48 p.m.
Thanks to everyone who replied.

Componentization seems the right thing to do and I'm looking at that now.

The 1.0 support to select root folders is interesting ; is this likely
to surface in a milestone release before GA ?

Jean-Michel Lemieux wrote:
As Geoff said, components are the first level of decomposition, but in
reality many projects already have a directory structure that they don't
want to split or refactor. There are a couple of things happening to
support finer grain loading that are being discussed in

https://jazz.net/jazz/web/projects/Jazz%20Project#action=com.ibm.team.workitem.viewWorkItem&id=42933


At a minimum we will support loading at any folder level for 1.0, a P2
is to remember this as you can with CVS modules or SVN externals.

Hope this helps.
Jean-Michel
Jazz Source Control Team

David Ward wrote:
Hi there

Using CVS over the years I've noticed that my team and others, often
use a CVS 'module' definition to work with a subset of a given CVS
project.

For example, my team does porting work for a large existing product.
We load the entire product source tree (> 1.2Gig) into CVS.
Throughout the development project, we need to work with a much
smaller (fixed) subset (say only 300MB) of that tree. We define a CVS
'module' that includes only the portion of the source that needs to be
worked on so that developers need not checkout gigabytes of data that
they mostly never use.

After that long-winded description ...

1) is there any equivalent feature in the Jazz SCM

and if not

2) do teams using the Jazz SCM ever face this need see a 'subset' view
of their code ?

Cheers
Dave

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.