<sect1 id="ajcore-introduction">
<title>Introduction</title>
- <para> When the compiler terminates abnormally, either because an abort message was
- issued or an exception was thrown, a AspectJ core file will be produced. You will
+ <para> When the compiler terminates abnormally, either because a particular kind of message was
+ issued or an exception was thrown, an AspectJ core file will be produced. You will
find it the working directory of the compiler and will have a name that contains
the date and time that the file was produced
e.g. <literal>ajcore.20060810.173655.626.txt</literal>. </para>
--- /dev/null
+body { \r
+ font-family: "Lucida Grande", "Trebuchet MS", sans-serif;\r
+ line-height: 1.1em;\r
+ }\r
+\r
+h1 {\r
+ margin-bottom: 3px;\r
+ padding-bottom: 0px;\r
+ line-height: 1.1em;\r
+}\r
+\r
+h2 { \r
+ font-size: 130%; \r
+ font-weight: bold ; \r
+ line-height: 16px;\r
+ color: #FFFFFF;\r
+ background-color: #0080C0;\r
+ padding: 5px;\r
+}\r
+\r
+h3 { \r
+ font-size: 110%; \r
+ font-weight: bold ; \r
+ line-height: 14px;\r
+ color: #FFFFFF;\r
+ background-color: orange;\r
+ padding: 5px;\r
+}\r
+\r
+tt { \r
+ font-size: 120%;\r
+ color: #00AAF0;\r
+ }\r
+\r
+tt tt { \r
+ font-size: 100%;\r
+ }\r
+\r
+.programlisting {\r
+ padding-top: 5px; \r
+ border: 2px solid #ccc;\r
+ background: #eee;\r
+ font-size: 120%;\r
+ color: #111199;\r
+\r
+ }\r
+\r
+.term { \r
+ color: #111199;\r
+ }\r
+\r
+.variablelist dd { \r
+ margin-left: 18px;\r
+ padding-left: 20px;\r
+ background: url(dd_arrow.gif) no-repeat 0 2px;\r
+ }\r
+\r
+.toc dt { \r
+ font-size: 110%;\r
+ padding-bottom: 0px;\r
+ margin-bottom: 5px;\r
+ }\r
+\r
+.toc dl dd dt { \r
+ font-size: 100%;\r
+ }\r
+\r
+.toc dt { \r
+ font-size: 100%\r
+ margin-bottom: 0;\r
+ }\r
+\r
+.informaltable table { \r
+ margin-left: 5%;\r
+ }\r
+\r
+.informaltable th { \r
+ background-color: orange;\r
+ padding: 1px;\r
+ }\r
+\r
+ul li { \r
+ line-height: 1.2em; \r
+ }\r
+\r
+.keyword { \r
+ font-weight: bold;\r
+ color: purple;\r
+ }
\ No newline at end of file
<title>Introduction</title>
<para> By default only warning and error messages are issued by the compiler whether it is
- being used for source code compilation, weaving, binary weaving or load-time weaving. </para>
+ being used for source code compilation, weaving, binary weaving or load-time weaving. Informational,
+ debug and weaving messages can also be obtained using compiler options or System properties. </para>
+
+ <sect2 id="configuration" xreflabel="configuration">
+ <title>Configuration</title>
+
+ <para> </para>
+ </sect2>
+
+ <sect2 id="examples" xreflabel="examples">
+ <title>Examples</title>
+
+ <para> </para>
+ </sect2>
</sect1>
</chapter>
<chapter id="trace" xreflabel="Trace">
- <title>Trace</title>
+ <title>Tracing</title>
<sect1 id="trace-introduction">
<title>Introduction</title>
the problem may relate to your specific environment where AspectJ is being used and will not be
reproducible by the AspectJ team. In one of these situations you may be asked to produce a
trace of the compiler when the problem occurs instead. This can then be attached to the bug report. </para>
+
+ <sect2 id="configuration" xreflabel="configuration">
+ <title>Configuration</title>
+
+ <para> When available (Java 5 or later) AspectJ will use the
+ <literal>java.util.logging</literal>
+ <ulink url="http://java.sun.com/j2se/1.5.0/docs/guide/logging/index.html">infrastructure</ulink>
+ that is configured using a logging.properties file. By default only error
+ and fatal events will be logged but less severe warnings as well as fine grained
+ method entry and exit events can be obtained using the appropriate configuration. All
+ compiler messages can also be logged through the infrastructure by setting the
+ <literal>org.aspectj.weaving.messages</literal> System property. </para>
+
+ <para> If you are using a JDK 1.4 or earlier AspectJ will use a simple built-in trace
+ infrastructure that logs to stderr. This is enabled by setting the
+ <literal>org.aspectj.weaving.tracing.enabled</literal> System property. You may also override
+ the default behaviour or provide your own trace implementation using the
+ <literal>org.aspectj.weaving.tracing.factory</literal> System property. </para>
+
+ <para> The table below lists the System properties that can be used to configure tracing. </para>
+ <informaltable>
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry>Property</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <literal>org.aspectj.tracing.debug</literal>
+ </entry>
+ <entry>
+ Enable simple debugging of the trace infrastructure itself.
+ <para> Default: <literal>false</literal>. </para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>org.aspectj.tracing.enabled</literal>
+ </entry>
+ <entry>
+ Enable the built-in AspectJ trace infrastructure.
+ <para> Default: <literal>false</literal>. </para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>org.aspectj.tracing.factory</literal>
+ </entry>
+ <entry>
+ Select trace infrastructure. Specify the fully qualified class name
+ of the <literal>org.aspectj.weaver.tools.TraceFactory</literal>
+ interface to use a custom infrastructure. Specify a value of
+ <literal>default</literal> to force AspectJ to use it's
+ built-in infrastructure.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>org.aspectj.tracing.messages</literal>
+ </entry>
+ <entry>
+ Enable tracing of compiler messages. The kind of messages logged
+ is determined by the selected trace infrastructure not the message
+ configuration.
+ <para> Default: <literal>false</literal>. </para>
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </sect2>
+
+ <sect2 id="examples" xreflabel="examples">
+ <title>Examples</title>
+
+ <para> </para>
+ </sect2>
</sect1>
</chapter>
projects / aspectj.git / commitdiff