It's all about the answers!

Ask a question

CC connector importer add a blankline between code lines


Guowei Jim Hu (1.0k910353) | asked Jul 22 '10, 7:38 a.m.
Just migrated a few base CC branchesto RTC streams, and the developers found outthat a different format in RTC for each and every file with double space between the lines. When we replace the checked out files from CC to RTC in order to check in them, we see these double spaces between lines are as conflicts when we compare with predecessors. So can you tell us which convention do we need to follow either the RTC format with double spaces or the usual file as it was earlier?

A blank line, which seems to be introduced during the migration from CC, between every 2 lines is not good for readability and maintainability of the code. Is it a known issue of the migration? Do we have an automated way to remove the extra blank lines that are introduced by the migration in all the files?
We want to check if there is a way to avoid this issue in the later migrations.

4 answers



permanent link
Geoffrey Clemm (30.1k33035) | answered Jul 22 '10, 8:24 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
You need to set the LINE_DELIMITER property in the CC synchronizer to
specifies what kind of line delimiters the text files in your CC VOB
actually have.

The synchronizer defaults to assuming that the VOB has Unix
line-endings, but your VOB must have Windows line-endings, so in the
ClearCase properties page of that synchronized stream, change the value
of the LINE_DELIMITER property from LF to CRLF.

For the files you've already imported, the easiest way to fix this is to
set this property of your synchronized stream, and re-import the files
(remove all the existing sync roots, and then add them back again).

Cheers,
Geoff

Note: In 3.0, we'll be

On 7/22/2010 7:53 AM, ghu wrote:
Just migrated a few base CC branchesto RTC streams, and the developers
found outthat a different format in RTC for each and every file with
double space between the lines. When we replace the checked out files
from CC to RTC in order to check in them, we see these double spaces
between lines are as conflicts when we compare with predecessors. So
can you tell us which convention do we need to follow either the RTC
format with double spaces or the usual file as it was earlier?

A blank line, which seems to be introduced during the migration from
CC, between every 2 lines is not good for readability and
maintainability of the code. Is it a known issue of the migration? Do
we have an automated way to remove the extra blank lines that are
introduced by the migration in all the files?
We want to check if there is a way to avoid this issue in the later
migrations.

permanent link
Guowei Jim Hu (1.0k910353) | answered Jul 22 '10, 1:57 p.m.
You need to set the LINE_DELIMITER property in the CC synchronizer to
specifies what kind of line delimiters the text files in your CC VOB
actually have.

The synchronizer defaults to assuming that the VOB has Unix
line-endings, but your VOB must have Windows line-endings, so in the
ClearCase properties page of that synchronized stream, change the value
of the LINE_DELIMITER property from LF to CRLF.

For the files you've already imported, the easiest way to fix this is to
set this property of your synchronized stream, and re-import the files
(remove all the existing sync roots, and then add them back again).



As I am using two-way sync., if I remove all files and folders in RTC while shutdown the sync. engine, when I start again to run import, how do I know it will not sync back the deletion changes back to CC and delete the files and folders in CC?

Do I have to remove the sync roots from all imported stream before to run the import again?

permanent link
Geoffrey Clemm (30.1k33035) | answered Jul 23 '10, 12:52 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
NOTE: When I say "remove the sync roots", I don't mean "delete the files
from ClearCase"! I mean:
- go to the sync stream view
- execute the "select files to synchronizer" operation
- check the "show existing sync roots" check box
- select all of the sync roots
- select "remove"

To avoid confusion, let me revise my instructions:

"Just delete the old sync stream (using the "delete" operation in the
sync stream view, *NOT* by deleting the branch in ClearCase!), and then
create a new sync stream (using the "create sync stream operation" in
the sync stream view).

Cheers,
Geoff

On 7/22/2010 2:07 PM, ghu wrote:
gmclemmwrote:
You need to set the LINE_DELIMITER property in the CC synchronizer to

specifies what kind of line delimiters the text files in your CC VOB

actually have.

The synchronizer defaults to assuming that the VOB has Unix
line-endings, but your VOB must have Windows line-endings, so in the

ClearCase properties page of that synchronized stream, change the
value
of the LINE_DELIMITER property from LF to CRLF.

For the files you've already imported, the easiest way to fix this
is to
set this property of your synchronized stream, and re-import the
files
(remove all the existing sync roots, and then add them back again).



As I am using two-way sync., if I remove all files and folders in RTC
while shutdown the sync. engine, when I start again to run import,
how do I know it will not sync back the deletion changes back to CC
and delete the files and folders in CC?

Do I have to remove the sync roots from all imported stream before to
run the import again?

permanent link
Geoffrey Clemm (30.1k33035) | answered Jul 23 '10, 2:07 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I got a followup question on this topic: What if I've already made some
changes on the Jazz side, that haven't been sync'ed over to ClearCase yet.?

After you have created the new sync stream, accept those change sets
(with the changes you haven't yet sync'ed to CC) into your merge
workspace for the new sync stream. You probably will be told that
you'll need to accept them as a "patch". That's fine ... go ahead and
create patches for them, and then accept those patches.

Cheers,
Geoff



On 7/23/2010 12:52 AM, Geoffrey Clemm wrote:
NOTE: When I say "remove the sync roots", I don't mean "delete the files
from ClearCase"! I mean:
- go to the sync stream view
- execute the "select files to synchronizer" operation
- check the "show existing sync roots" check box
- select all of the sync roots
- select "remove"

To avoid confusion, let me revise my instructions:

"Just delete the old sync stream (using the "delete" operation in the
sync stream view, *NOT* by deleting the branch in ClearCase!), and then
create a new sync stream (using the "create sync stream operation" in
the sync stream view).

Cheers,
Geoff

On 7/22/2010 2:07 PM, ghu wrote:
gmclemmwrote:
You need to set the LINE_DELIMITER property in the CC synchronizer to

specifies what kind of line delimiters the text files in your CC VOB

actually have.

The synchronizer defaults to assuming that the VOB has Unix
line-endings, but your VOB must have Windows line-endings, so in the

ClearCase properties page of that synchronized stream, change the
value
of the LINE_DELIMITER property from LF to CRLF.

For the files you've already imported, the easiest way to fix this
is to
set this property of your synchronized stream, and re-import the
files
(remove all the existing sync roots, and then add them back again).



As I am using two-way sync., if I remove all files and folders in RTC
while shutdown the sync. engine, when I start again to run import,
how do I know it will not sync back the deletion changes back to CC
and delete the files and folders in CC?

Do I have to remove the sync roots from all imported stream before to
run the import again?

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.