Synchronizer selected directories not synching recursively
RTC 2.0 CC synchronized stream, select CC files. When I add a directory to the list, only the directory is synchronized, not the underlying directory structure.
When I browse, checking a directory does not check the underlying elements. It adds just the directory name to the list, which has the same effect as directly adding the directory name to the list.
The result is, I have to browse, expand the entire structure, and select every element/directory individually. Not what I expected.
I cannot find an option anywhere to say recurse, leading me to believe it should do so automatically since not recursing makes no sense
Have I missed something?
When I browse, checking a directory does not check the underlying elements. It adds just the directory name to the list, which has the same effect as directly adding the directory name to the list.
The result is, I have to browse, expand the entire structure, and select every element/directory individually. Not what I expected.
I cannot find an option anywhere to say recurse, leading me to believe it should do so automatically since not recursing makes no sense
Have I missed something?
8 answers
Yes, selecting a folder means that this folder and all of its members
(recursively) will be synchronized.
So there are two bugs here:
(1) the documentation should make that clear
(2) this is what should have happened when you synchronized.
For (1), I've submitted work item 99430
FOr (2), please submit a defect work item, so we can find out what's
going on.
Cheers,
Geoff
jim.islandtraining.com wrote:
(recursively) will be synchronized.
So there are two bugs here:
(1) the documentation should make that clear
(2) this is what should have happened when you synchronized.
For (1), I've submitted work item 99430
FOr (2), please submit a defect work item, so we can find out what's
going on.
Cheers,
Geoff
jim.islandtraining.com wrote:
RTC 2.0 CC synchronized stream, select CC files. When I add a
directory to the list, only the directory is synchronized, not the
underlying directory structure.
When I browse, checking a directory does not check the underlying
elements. It adds just the directory name to the list, which has the
same effect as directly adding the directory name to the list.
The result is, I have to browse, expand the entire structure, and
select every element/directory individually. Not what I expected.
I cannot find an option anywhere to say recurse, leading me to believe
it should do so automatically since not recursing makes no sense
Have I missed something?
Regarding (2) I think this may just be a case of being confused by what the UI is doing. As Geoff said, selecing a folder means that this folder and all of its children will be synchronized. This makes the folder a "synchronization root." If you select the children explicitly I believe that will make them also "synchronization roots" which is not what you want.
Carol
Carol
Yes, selecting a folder means that this folder and all of its members
(recursively) will be synchronized.
So there are two bugs here:
(1) the documentation should make that clear
(2) this is what should have happened when you synchronized.
For (1), I've submitted work item 99430
FOr (2), please submit a defect work item, so we can find out what's
going on.
Cheers,
Geoff
jim.islandtraining.com wrote:
RTC 2.0 CC synchronized stream, select CC files. When I add a
directory to the list, only the directory is synchronized, not the
underlying directory structure.
When I browse, checking a directory does not check the underlying
elements. It adds just the directory name to the list, which has the
same effect as directly adding the directory name to the list.
The result is, I have to browse, expand the entire structure, and
select every element/directory individually. Not what I expected.
I cannot find an option anywhere to say recurse, leading me to believe
it should do so automatically since not recursing makes no sense
Have I missed something?
The question is what Jim meant when he said:
"When I add a directory to the list, only the directory is synchronized,
not the underlying directory structure."
If Jim meant "he didn't see the children checked in the GUI", then as
Carol says, it's just a misinterpretation of the GUI.
If on the other hand, Jim meant "when I invoke a synchronize operation,
the children don't get synchronized", then that would be a bug.
If we don't see a work item, we'll assume Carol was right, and it was
just a misinterpretation of the GUI (:-).
Cheers,
Geoff
cdyutkow wrote:
"When I add a directory to the list, only the directory is synchronized,
not the underlying directory structure."
If Jim meant "he didn't see the children checked in the GUI", then as
Carol says, it's just a misinterpretation of the GUI.
If on the other hand, Jim meant "when I invoke a synchronize operation,
the children don't get synchronized", then that would be a bug.
If we don't see a work item, we'll assume Carol was right, and it was
just a misinterpretation of the GUI (:-).
Cheers,
Geoff
cdyutkow wrote:
Regarding (2) I think this may just be a case of being confused by
what the UI is doing. As Geoff said, selecing a folder means that
this folder and all of its children will be synchronized. This makes
the folder a "synchronization root." If you select the
children explicitly I believe that will make them also
"synchronization roots" which is not what you want.
Carol
gmclemmwrote:
Yes, selecting a folder means that this folder and all of its members
(recursively) will be synchronized.
So there are two bugs here:
(1) the documentation should make that clear
(2) this is what should have happened when you synchronized.
For (1), I've submitted work item 99430
FOr (2), please submit a defect work item, so we can find out what's
going on.
Cheers,
Geoff
jim.islandtraining.com wrote:
RTC 2.0 CC synchronized stream, select CC files. When I add a
directory to the list, only the directory is synchronized, not the
underlying directory structure.
When I browse, checking a directory does not check the underlying
elements. It adds just the directory name to the list, which has
the
same effect as directly adding the directory name to the list.
The result is, I have to browse, expand the entire structure, and
select every element/directory individually. Not what I expected.
I cannot find an option anywhere to say recurse, leading me to
believe
it should do so automatically since not recursing makes no sense
Have I missed something?
Even if the children don't get synchronized, it still might not be a bug. If it is a base ClearCase sync stream for which the selection of files was made by a label -- and if the directory itself has that label but the children don't, then the children won't be synchronized.
But otherwise, it would be a bug :-)
Carol
But otherwise, it would be a bug :-)
Carol
The question is what Jim meant when he said:
"When I add a directory to the list, only the directory is synchronized,
not the underlying directory structure."
If Jim meant "he didn't see the children checked in the GUI", then as
Carol says, it's just a misinterpretation of the GUI.
If on the other hand, Jim meant "when I invoke a synchronize operation,
the children don't get synchronized", then that would be a bug.
If we don't see a work item, we'll assume Carol was right, and it was
just a misinterpretation of the GUI (:-).
Cheers,
Geoff
cdyutkow wrote:
Regarding (2) I think this may just be a case of being confused by
what the UI is doing. As Geoff said, selecing a folder means that
this folder and all of its children will be synchronized. This makes
the folder a "synchronization root." If you select the
children explicitly I believe that will make them also
"synchronization roots" which is not what you want.
Carol
gmclemmwrote:
Yes, selecting a folder means that this folder and all of its members
(recursively) will be synchronized.
So there are two bugs here:
(1) the documentation should make that clear
(2) this is what should have happened when you synchronized.
For (1), I've submitted work item 99430
FOr (2), please submit a defect work item, so we can find out what's
going on.
Cheers,
Geoff
jim.islandtraining.com wrote:
RTC 2.0 CC synchronized stream, select CC files. When I add a
directory to the list, only the directory is synchronized, not the
underlying directory structure.
When I browse, checking a directory does not check the underlying
elements. It adds just the directory name to the list, which has
the
same effect as directly adding the directory name to the list.
The result is, I have to browse, expand the entire structure, and
select every element/directory individually. Not what I expected.
I cannot find an option anywhere to say recurse, leading me to
believe
it should do so automatically since not recursing makes no sense
Have I missed something?
I would argue that if that file isn't labeled, then it isn't a child (at
least, from the perspective of that view :-). But that's just a
terminological question ... I agree with essence of Carol's clarification.
Cheers,
Geoff
cdyutkow wrote:
least, from the perspective of that view :-). But that's just a
terminological question ... I agree with essence of Carol's clarification.
Cheers,
Geoff
cdyutkow wrote:
Even if the children don't get synchronized, it still might not be a
bug. If it is a base ClearCase sync stream for which the selection
of files was made by a label -- and if the directory itself has that
label but the children don't, then the children won't be
synchronized.
But otherwise, it would be a bug :-)
CarolThe question is what Jim meant when he
said:
"When I add a directory to the list, only the directory is
synchronized,
not the underlying directory structure."
If Jim meant "he didn't see the children checked in the
GUI", then as
Carol says, it's just a misinterpretation of the GUI.
If on the other hand, Jim meant "when I invoke a synchronize
operation,
the children don't get synchronized", then that would be a bug.
If we don't see a work item, we'll assume Carol was right, and it was
just a misinterpretation of the GUI (:-).
Cheers,
Geoff
cdyutkow wrote:
Regarding (2) I think this may just be a case of being confused by
what the UI is doing. As Geoff said, selecing a folder means that
this folder and all of its children will be synchronized. This
makes
the folder a "synchronization root." If you select the
children explicitly I believe that will make them also
"synchronization roots" which is not what you want.
Carol
gmclemmwrote:
Yes, selecting a folder means that this folder and all of its
members
(recursively) will be synchronized.
So there are two bugs here:
(1) the documentation should make that clear
(2) this is what should have happened when you synchronized.
For (1), I've submitted work item 99430
FOr (2), please submit a defect work item, so we can find out
what's
going on.
Cheers,
Geoff
jim.islandtraining.com wrote:
RTC 2.0 CC synchronized stream, select CC files. When I add a
directory to the list, only the directory is synchronized, not the
underlying directory structure.
When I browse, checking a directory does not check the underlying
elements. It adds just the directory name to the list, which has
the
same effect as directly adding the directory name to the list.
The result is, I have to browse, expand the entire structure, and
select every element/directory individually. Not what I expected.
I cannot find an option anywhere to say recurse, leading me to
believe
it should do so automatically since not recursing makes no sense
Have I missed something?
Problem
CRJAZ0977I The "com.ibm.team.jazz.foundation.express" server license policy does not allow the "Save Data Set Definition" operation.
Reason
Further information on licensing is available in the help topic on editions and licenses.
Customizable work item workflow
Plan risk assessment
Reports
Role based process permissions
ClearCase Synchronizer
ClearCase Bridge
ClearQuest Connector
ClearQuest record and Jazz work item bridge
LDAP import
Floating licenses available
High availability
Jim, just to clarify. You are using 2.0? or 2.0.0.1?
RTC 2.0 CC synchronized stream, select CC files. When I add a directory to the list, only the directory is synchronized, not the underlying directory structure.
When I browse, checking a directory does not check the underlying elements. It adds just the directory name to the list, which has the same effect as directly adding the directory name to the list.
The result is, I have to browse, expand the entire structure, and select every element/directory individually. Not what I expected.
I cannot find an option anywhere to say recurse, leading me to believe it should do so automatically since not recursing makes no sense
Have I missed something?
I've been unable to duplicate the problem using 2.0.0.1/Windows, which I happened to have installed and handy to test on.
I'll try with the 2.0 bits.
2 more questions:
What platform ??
How deep into the VOB's directory tree is the root you're trying to import?
I'll try with the 2.0 bits.
2 more questions:
What platform ??
How deep into the VOB's directory tree is the root you're trying to import?
RTC 2.0 CC synchronized stream, select CC files. When I add a directory to the list, only the directory is synchronized, not the underlying directory structure.
When I browse, checking a directory does not check the underlying elements. It adds just the directory name to the list, which has the same effect as directly adding the directory name to the list.
The result is, I have to browse, expand the entire structure, and select every element/directory individually. Not what I expected.
I cannot find an option anywhere to say recurse, leading me to believe it should do so automatically since not recursing makes no sense
Have I missed something?