How to use another source code editor without problem
I'm using another source code editor than eclipse for my development and this tool does not have any plugin that would allow me to work with RTC.
I have had some bad surprise with some conflicting changes that took me hours to solve.
For example I had hard time when a conflict resulted from a class I renamed has been modified by someone else on the same time.
I want to know what operation should be done inside Eclispe/RTC to avoid this kind of problems.
Thanks.
I have had some bad surprise with some conflicting changes that took me hours to solve.
For example I had hard time when a conflict resulted from a class I renamed has been modified by someone else on the same time.
I want to know what operation should be done inside Eclispe/RTC to avoid this kind of problems.
Thanks.
2 answers
What version of RTC are you using? If it is 2.0.0.2 or later, you can perform a refresh of the local sandbox from the Refresh dropdown menu found in the toolbar of the Pending Changes view. There is also a preference that can be enabled on the Team>Jazz Source Control>Local Changes panel that will check for local changes before performing certain SCM operation. On that same preference page, you can enable the backup shed which will make backups of any local files that get overwritten by SCM operations so you can retrieve them if needed.
Hope this helps,
Michael
Hope this helps,
Michael
I'm using another source code editor than eclipse for my development and this tool does not have any plugin that would allow me to work with RTC.
I have had some bad surprise with some conflicting changes that took me hours to solve.
For example I had hard time when a conflict resulted from a class I renamed has been modified by someone else on the same time.
I want to know what operation should be done inside Eclispe/RTC to avoid this kind of problems.
Thanks.
You should do all operations that involve either renaming or moving
files either:
- inside of Eclipse
- inside of Visual Studio
- through the RTC SCM web browser, or
- through the RTC SCM command tool.
All other operations such as those that delete files, create new files,
or modify the content of existing files, can all be done equally well
directly against the file area where the source-controlled files are
loaded (the "sandbox").
Note: If you do moves or renames directly against the file system, then
when RTC scans the file system for changes, those look like the deletion
of the file at the old pathname, and a creation of a new file at the new
pathname. Although one could imagine scanning for files that have the
same content, commonly the content is changed in addition to the
move/rename (such as in your case), so this wouldn't help much.
Cheers,
Geoff
On 10/27/2010 9:53 AM, GAme wrote:
files either:
- inside of Eclipse
- inside of Visual Studio
- through the RTC SCM web browser, or
- through the RTC SCM command tool.
All other operations such as those that delete files, create new files,
or modify the content of existing files, can all be done equally well
directly against the file area where the source-controlled files are
loaded (the "sandbox").
Note: If you do moves or renames directly against the file system, then
when RTC scans the file system for changes, those look like the deletion
of the file at the old pathname, and a creation of a new file at the new
pathname. Although one could imagine scanning for files that have the
same content, commonly the content is changed in addition to the
move/rename (such as in your case), so this wouldn't help much.
Cheers,
Geoff
On 10/27/2010 9:53 AM, GAme wrote:
I'm using another source code editor than eclipse for my development
and this tool does not have any plugin that would allow me to work
with RTC.
I have had some bad surprise with some conflicting changes that took
me hours to solve.
For example I had hard time when a conflict resulted from a class I
renamed has been modified by someone else on the same time.
I want to know what operation should be done inside Eclispe/RTC to
avoid this kind of problems.
Thanks.