[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[jdt-ui-dev] Tracing the JDT/Core plugin activity
|
From build 20011107 on, we have released a ".options" file inside our
plugin which can be used as a template for activating traces inside the
JDT/Core area. It is using the generic Eclipse debug mode which means that
you need to perform the following steps before seeing the JDT/Core traces:
Copy our .options template file located at <installLocation>/plugins/org.eclipse.jdt.core/.options up to the <installLocation> next to the Eclipse.exe file.
Start Eclipse in debug mode using the -debug extra command line argument.
Example of an JDT/Core .options file:
org.eclipse.jdt.core/debug=true
org.eclipse.jdt.core/debug/indexmanager=true
org.eclipse.jdt.core/debug/compiler=true
org.eclipse.jdt.core/debug/javamodel=true
org.eclipse.jdt.core/debug/javadelta=true
org.eclipse.jdt.core/debug/hierarchy=true
org.eclipse.jdt.core/debug/builder=true
Debug tracing the JDT/Core can lead to a lot of messages to be dumped out,
therefore you can further edit the .options file in order to turn off uninteresting traces. Here is what can be
selectively chosen:
org.eclipse.jdt.core/debug/indexmanager=true
Enable tracing of background indexing process. It will indicate all
interactions with the indexer, either when modifying the index files and
or performing queries in them.
org.eclipse.jdt.core/debug/compiler=true
Enable tracing of all actual Java compiler activity.
org.eclipse.jdt.core/debug/javamodel=true
Enable tracing of the Java Model lazy populating. It will indicate when
actually opening/closing a Java element.
org.eclipse.jdt.core/debug/javadelta=true
Enable tracing of the Java element deltas which are fired to listeners.
org.eclipse.jdt.core/debug/hierarchy=true
Enable tracing of the type hierarchy computation.
org.eclipse.jdt.core/debug/builder=true
Enable tracing of the Java builder activity. The Java builder is driving
the incremental recompilation aspects, and this trace can be used to
understand why a given file actually got triggered for recompilation. Note
that this trace is not yet fully implemented given the Java builder is
under rework.
