1. Debugging RTC CLI in Eclipse

2. Overview Create a client installation based on an Ella build
Optionally make a copy of this installation
Set up client for debugging
Create a debug configuration
Update jars in client installation
Debug

3. Create a client installation based on an Ella build
I used the Full Client Zip
RTC-Client-Win64_ M3-RTC-I zip Windows 64-bit RTC Client

4. Optionally make a copy of this installation
You will modify the client installation to make it debuggable.
You might want to keep a standard client installation available, for convenience.

5. Set up client for debugging
cd RTC_HOME\jazz\scmtools\eclipse
Edit scm.ini file
Add the following two lines at the end of the - vmargs section
-Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=7777
This will cause the CLI to wait for the debugger to connect to it.
C:\RTC-Client-Debug\jazz\scmtools\eclipse>scm help
<JIT: FullSpeedDebug: ignoring countString>
Listening for transport dt_socket at address: 7777

6. Create a debug configuration
Start an Eclipse client on the jazzdev server.
Click Run->Debug Configurations

7. Create a debug configuration
Right click on “Remote Java Application” and select “New”
Give your new configuration a name (e.g., CLI Remote).
Port must match the address you used in the scm.ini file (e.g., 7777).
Project should be “com.ibm.team.filesystem.cli.core”.
Connection Type should be “Standard (Socket Attach)”.
Host can be “localhost” if you are running the CLI on the local host, or another hostname if you are running your CLI on another computer.

8. Create a debug configuration

9. Create a debug configuration
In the Source tab, add all of your projects, so you can see the source and set breakpoints.

10. Start debugging

11. Start Debugging

12. Start Debugging

13. Debugging with code changes
The code being executed is in the installation area, not in Eclipse.
Therefore, if you modify any code, you need to build and export, and update the installation area.
Make sure code version matches installation area.
Alternatively, the install area can be modified so it runs class files from your workspace.