3.5. Troubleshooting Buckminster problems

3.5.1. Errors and Warnings

WARNING [0072] : Component request org.junit:osgi.bundle is in conflict ...

This error message is displayed during workspace materialization, and can be ignored:

WARNING [nnnn] : Component request org.junit:osgi.bundle/[4.8.1.v4_8_1_v20100427-1100,4.8.1.v4_8_1_v20100427-1100] is inconflict with
                 request org.junit:osgi.bundle/[3.8.2.v3_8_2_v20100427-1100,3.8.2.v3_8_2_v20100427-1100]

It occurs because the org.eclipse.jdt feature depends on two different versions of org.junit, namely JUnit 3 and JUnit 4.

Resource ‘/.buckminster/tp’ is not local

This error message appears at the end of materialization (during the refresh). It is benign and can be ignored (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=310850):

Problems during metadata refresh
E Resource '/.buckminster/tp' is not local

3.5.2. Troubleshooting techniques

These techniques may assist in resolving Buckminster problems:

3.5.2.1. Problems in the Eclipse IDE

  1. Before re-executing a Buckminster action, clear any previous error messages to avoid confusion
    Right-click in the Error Log view, and select Delete Log
    Right-click in the Console view, and select Clear
    Right-click in the Console view, and select Remove All Terminated
  2. Refresh all Buckminster metadata (sometimes this becomes stale)

    Go to Window ‣ Preferences ‣ Buckminster, and click Clear URL cache and Refresh Meta-data

  3. Restart Eclipse (certain workspace changes are not recognised by Buckminster until Eclipse is restarted)

  4. Increase the logging level
    Go to Window ‣ Preferences ‣ Buckminster, and set Console logger level: to DEBUG
    Go to Window ‣ Preferences ‣ Buckminster ‣ Console, and deselect Limit console output
  5. Disable parallel materialization
    By default materialization is performed in multiple threads, which makes the logging output difficult to read
    Go to Window ‣ Preferences ‣ Buckminster, and set Max number of parallel materializations to 1
    Go to Window ‣ Preferences ‣ Buckminster, and set Maximum number of resolver threads to 1

3.5.2.2. Problems with headless Buckminster

  1. Increase the logging level