Why is a IXIASOFT CCMS plugin or dropin not loading?

You need to obtain debug information on the plugins and dropins so you can investigate the cause of the failure.

Symptom

One or more plugins or dropins are not loading.

Problem

You might be missing some library dependencies or some platform conditions are not being met.

Solution

Run Eclipse in debug mode with an ".options" file to have the IXIASOFT CCMS Eclipse Client produce the debug.txt file which contains special debug information on each loaded plugin or dropin.

To obtain the debug.txt:

  1. Create a text file containing the following content: 
    org.eclipse.equinox.p2.core/debug=true
org.eclipse.equinox.p2.core/reconciler=true
org.eclipse.equinox.p2.director/debug=true
org.eclipse.equinox.p2.engine/debug=true
  2. Save the file as .options in the same folder as the eclipse.ini file for your IXIASOFT CCMS Eclipse Client. For example, the file can be saved as .options in C:\eclipses\eclipse-Prod42.
    Note: To rename the file .options, you can open a command prompt and run the rename command in the folder where you created the file; for example, C:\eclipses\eclipse-Prod42>ren foo.txt .options, which will rename foo.txt to .options.
  3. Right-click the IXIASOFT CCMS Eclipse shortcut.
  4. Click Properties.
  5. Click the Shortcut tab.
  6. Copy the contents of the Target box so you can revert to it easily later.
  7. In the Target box, change the target as follows:
    • Change eclipse.exe for eclipsec.exe.
    • Add these parameters to the end of the line: -clean -console -consoleLog -debug
    • Add the following at the end of the line after the parameters: >debug.txt 2>&1. For example: 
      C:\eclipses\eclipse-Prod42\eclipsec.exe -clean -console -consoleLog -debug >debug.txt 2>&1
  8. Click OK.
  9. Double-click the shortcut to launch the IXIASOFT CCMS Eclipse Client.
  10. Review the debug.txt.
  11. When you no longer need debug mode, revert the contents of the Target box to the original target.