Remove indentation from <programlisting> blocks in docs

Many dozens (hundreds?) of documentation code blocks were indented to
match the surrounding XML or just arbitrarily. The thing is: Inside
<programlisting> tags, similar to <pre> tags, line feeds and leading
whitespace are being preserved, which looked very awkward in the HTML
documentation. While a few files were mostly correct in this respect,
which shows that it was meant to be like that, many others were not.
This was tedious, stupid work to fix, but it had to be done.

Please note that the documentation was in no way updated content-wise.
This is also overdue, but not my focus here.

Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>

4 files changed, 159 insertions, 159 deletions

diff --git a/docs/pdGuideDB/ajcore.xml b/docs/pdGuideDB/ajcore.xml
index 3ca82849f..7207df3cc 100644
--- a/docs/pdGuideDB/ajcore.xml
+++ b/docs/pdGuideDB/ajcore.xml
@@ -1,26 +1,26 @@
 <chapter id="ajcore" xreflabel="AspectJ Core Files">
     <title>AspectJ Core Files</title>
-    
+
     <sect1 id="ajcore-introduction">
         <title>Introduction</title>
-        
+
         <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 it will have a name that contains
-        the date and time that the file was produced 
+        the date and time that the file was produced
         e.g. <literal>ajcore.20060810.173655.626.txt</literal>. The file contains details
         of the problem such as the exception thrown as well as information about the
         environment such as operating system and Java version. When submitting a bug,
         include this file whenever it is available.</para>
-            
+
         <sect2 id="configuration" xreflabel="configuration">
             <title>Configuring dump files</title>
-            
-            <para> By default AspectJ will only create an <literal>ajcore</literal> file 
-            when an unexpected exception is thrown by the weaver or an 
+
+            <para> By default AspectJ will only create an <literal>ajcore</literal> file
+            when an unexpected exception is thrown by the weaver or an
             <literal>abort</literal> message is
             issued. However it is possible to disable this feature or enable files to
-            be produced under different circumstances. The table below lists the System 
+            be produced under different circumstances. The table below lists the System
             properties that can be used to configure <literal>ajcore</literal> files. </para>
             <informaltable>
                 <tgroup cols="3">
@@ -52,7 +52,7 @@
                             </entry>
                             <entry>
                             	Message kind for which to generate <literal>ajcore</literal>
-                            	e.g. <literal>error</literal>. 
+                            	e.g. <literal>error</literal>.
                             </entry>
                         </row>
                         <row>
@@ -63,7 +63,7 @@
                                 <literal>none</literal>
                             </entry>
                             <entry>
-                            	The directory used for ajcore files. 
+                            	The directory used for ajcore files.
                             </entry>
                         </row>
                     </tbody>
@@ -73,7 +73,7 @@
 
         <sect2 id="ajcore-examples" xreflabel="AJCore File Examples">
             <title>AJCore File Examples</title>
-        
+
             <para> Below is an extract from an <literal>ajcore</literal> file. You will see
             details of the dump configuration as well as the exception (with stack trace) that
             is the source of the problem and any messages issued by the compiler. Most importantly
@@ -191,8 +191,8 @@ java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
 	at org.aspectj.tools.ajc.Main.run(Main.java:367)
 	at org.aspectj.tools.ajc.Main.runMain(Main.java:246)
 	at org.aspectj.tools.ajc.Main.main(Main.java:86)
-			]]></programlisting>
-            
+]]>       </programlisting>
+
         </sect2>
     </sect1>
 </chapter>
diff --git a/docs/pdGuideDB/ltwdump.xml b/docs/pdGuideDB/ltwdump.xml
index a17ceae5b..72554d043 100644
--- a/docs/pdGuideDB/ltwdump.xml
+++ b/docs/pdGuideDB/ltwdump.xml
@@ -1,55 +1,55 @@
 <chapter id="ltwdump" xreflabel="Dumping classes during load-time weaving">
     <title>Dumping classes during load-time weaving</title>
-    
+
     <sect1 id="ltwdump-introduction">
         <title>Introduction</title>
-        
-        <para> 
-        	Very rarely problems may be encountered with classes that have been 
+
+        <para>
+        	Very rarely problems may be encountered with classes that have been
         	load-time woven.
-        	Symptoms will include incorrect program function or a Java exception such as 
+        	Symptoms will include incorrect program function or a Java exception such as
         	<literal>java.lang.VerifyError</literal>.
-            In these situations it's most helpful to include the offending class 
-            in the bug report. When using load-time weaving the woven classes are 
+            In these situations it's most helpful to include the offending class
+            in the bug report. When using load-time weaving the woven classes are
             in memory only so to save them to disk configure
-            <literal>META-INF/aop.xml</literal> to dump the classes (by default 
-            to an <literal>_ajdump</literal> subdirectory of the current working 
-            directory).  Also if the input class file is not available 
+            <literal>META-INF/aop.xml</literal> to dump the classes (by default
+            to an <literal>_ajdump</literal> subdirectory of the current working
+            directory).  Also if the input class file is not available
             (e.g. it is a generated proxy or has already been instrumented by another agent)
             you can configure the weaver to dump the input classes as well.
         </para>
         <sect2 id="ltw-examples" xreflabel="ltwdump-configuration">
             <title>Configuring bytecode dumping in load-time weaving</title>
             <para>
-  			For details of how to configure byte-code dumping, see the             
-            AspectJ Development Environment Guide section on 
+  			For details of how to configure byte-code dumping, see the
+            AspectJ Development Environment Guide section on
 				<ulink url="../devguide/ltw-configuration.html#configuring-load-time-weaving-with-aopxml-files">
-				Configuring Load-time Weaving</ulink>.  
+				Configuring Load-time Weaving</ulink>.
             Following is a simple example.
             </para>
             </sect2>
 
         <sect2 id="ltwdump-examples" xreflabel="LTW Dump Examples">
             <title>LTW Dump Examples</title>
-                    
-            <para> The following <literal>META-INF/aop.xml</literal> will 
+
+            <para> The following <literal>META-INF/aop.xml</literal> will
             weave classes in the <literal>com.foo</literal> package (and subpackages) but not
-            CGLIB generated classes in the <literal>com.foo.bar</literal> package (and subpackages). 
+            CGLIB generated classes in the <literal>com.foo.bar</literal> package (and subpackages).
             It will also ensure all
             woven byte-code is dumped both before and after weaving. </para>
 	        <programlisting><![CDATA[
-	<aspectj>
-		<aspects>
-			<aspect name="ataspectj.EmptyAspect"/>
-		</aspects>
-	    <weaver options="-verbose -debug">
-	        <dump within="com.foo.bar..*" beforeandafter="true"/> 
-    	    <include within="com.foo..*"/>
-        	<exclude within="com.foo.bar..*CGLIB*"/>
-		</weaver>
-	</aspectj>
-			]]></programlisting>
-            
+<aspectj>
+    <aspects>
+        <aspect name="ataspectj.EmptyAspect"/>
+    </aspects>
+    <weaver options="-verbose -debug">
+        <dump within="com.foo.bar..*" beforeandafter="true"/>
+        <include within="com.foo..*"/>
+        <exclude within="com.foo.bar..*CGLIB*"/>
+    </weaver>
+</aspectj>
+]]></programlisting>
+
             <para> You should see messages similar to this: </para>
 
 	        <programlisting><![CDATA[
@@ -59,15 +59,15 @@
 [WeavingURLClassLoader] info register aspect ataspectj.EmptyAspect
 [WeavingURLClassLoader] debug not weaving 'com.foo.bar.Test$$EnhancerByCGLIB$$12345'
 [WeavingURLClassLoader] debug weaving 'com.foo.bar.Test'
-			]]></programlisting>
-            
+]]></programlisting>
+
             <para> On disk you would find the following files: </para>
 
 	        <programlisting><![CDATA[
-	_ajdump/_before/com/foo/bar/Test.class
-	_ajdump/com/foo/bar/Test.class
-			]]></programlisting>
-            
+_ajdump/_before/com/foo/bar/Test.class
+_ajdump/com/foo/bar/Test.class
+]]></programlisting>
+
         </sect2>
     </sect1>
 </chapter>
diff --git a/docs/pdGuideDB/messages.xml b/docs/pdGuideDB/messages.xml
index 8d2a2ab97..9d2caf0b5 100644
--- a/docs/pdGuideDB/messages.xml
+++ b/docs/pdGuideDB/messages.xml
@@ -1,6 +1,6 @@
 <chapter id="messages" xreflabel="Messages">
     <title>Messages</title>
-    
+
     <sect1 id="messages-introduction">
         <title>Introduction</title>
         <para>
@@ -11,47 +11,47 @@
             which are hidden. However, when investigating
             unexpected behavior it's helpful to show them.  This section describes how
             to configure messages, presents some problem scenarios when
-            compiling or doing load-time weaving, and summarizes some of the 
+            compiling or doing load-time weaving, and summarizes some of the
             more relevant messages.
         </para>
-        <sect2 id="messages-introduction-config" 
+        <sect2 id="messages-introduction-config"
             xreflabel="messages-configuration">
             <title>Configuring Messages</title>
             <para>
-                The compiler offers <literal>-verbose</literal>, 
-                <literal>-warning</literal>, and <literal>-XLint</literal> options 
-                when invoked using the command-line, Ant, or embedded in an IDE.  
-                All options are listed in the AspectJ Development Environment Guide 
-                sections for 
-                <ulink url="../devguide/ajc-ref.html">Ajc</ulink> and 
+                The compiler offers <literal>-verbose</literal>,
+                <literal>-warning</literal>, and <literal>-XLint</literal> options
+                when invoked using the command-line, Ant, or embedded in an IDE.
+                All options are listed in the AspectJ Development Environment Guide
+                sections for
+                <ulink url="../devguide/ajc-ref.html">Ajc</ulink> and
                 <ulink url="../devguide/antTasks-iajc.html">Ant Tasks</ulink>.
-                The <ulink url="../devguide/ltw.html">Load-time Weaving</ulink> 
+                The <ulink url="../devguide/ltw.html">Load-time Weaving</ulink>
                 section describes how to use XML configuration files and
                 system properties to pass options to the weaver.  (You can also
                 pass options to the weaver using system properties in build-
-                time weaving.) 
+                time weaving.)
                 The <literal>-verbose</literal> option has the effect of including
                 messages level "info", which are normally ignored.
                 Both <literal>warning</literal> and <literal>XLint</literal>
-                enable you to identify specific messages to emit, but warning 
-                messages tend to be the same provided by the underlying Eclipse 
-                JDT (Java) compiler, while XLint messages are emitted by the 
+                enable you to identify specific messages to emit, but warning
+                messages tend to be the same provided by the underlying Eclipse
+                JDT (Java) compiler, while XLint messages are emitted by the
                 AspectJ compiler or weaver.  Obviously, during load-time weaving
                 only weaver messages will be emitted.  Similarly, if aspects
                 are compiled but not woven, then only compiler messages will be
                 emitted.  However, the usual case for the compiler/weaver working
                 at build time is to emit both compiler and weaver messages.
             </para>
-            
-            <para> The tables below list some options, System Properties (for LTW only) and Java 5 annotations 
+
+            <para> The tables below list some options, System Properties (for LTW only) and Java 5 annotations
             used to control AspectJ messages. The method
-            of configuration depends on your environment so please refer to the relevant 
-            documentation for 
-            <ulink url="../devguide/ajc-ref.html">ajc</ulink>, 
-            <ulink url="../devguide/antTasks.html">Ant</ulink> or 
-            <ulink url="../devguide/ltw-configuration.html#weaver-options">LTW</ulink>. 
+            of configuration depends on your environment so please refer to the relevant
+            documentation for
+            <ulink url="../devguide/ajc-ref.html">ajc</ulink>,
+            <ulink url="../devguide/antTasks.html">Ant</ulink> or
+            <ulink url="../devguide/ltw-configuration.html#weaver-options">LTW</ulink>.
             </para>
-            
+
             <para>
             <informaltable>
                 <tgroup cols="2">
@@ -105,15 +105,15 @@
                             </entry>
                             <entry>
                             	In Ant tasks and LTW respectively specify the class to receive all messages.
-                                See 
+                                See
                                 <ulink url="../devguide/antTasks-iajc.html#antTasks-iajc-options">
                                 iajc task options</ulink> or
                                 <ulink url="../devguide/ltw-configuration.html#weaver-options">
                                 Weaver Options</ulink>.
                             </entry>
                         </row>
-                        
-<!-- We need full javadoc for this API                       
+
+<!-- We need full javadoc for this API
                         <row>
                             <entry>
                                 <literal>org.aspectj.tools.Main.setMessageHolder(..)</literal>
@@ -123,7 +123,7 @@
                                 outside of Ant.
                             </entry>
                         </row>
--->                        
+-->
                     </tbody>
                 </tgroup>
             </informaltable>
@@ -144,7 +144,7 @@
                                 <literal>aj.weaving.verbose</literal>
                             </entry>
                             <entry>
-                            	 Show informational messages including AspectJ version and build date 
+                            	 Show informational messages including AspectJ version and build date
                             	 (same as <literal>-verbose</literal> option).
                             </entry>
                         </row>
@@ -162,7 +162,7 @@
                                 <literal>org.aspectj.weaving.messages</literal>
                             </entry>
                             <entry>
-                            	Set this system property to enable tracing of all compiler 
+                            	Set this system property to enable tracing of all compiler
                             	messages. See <xref linkend="trace-configuration"/>.
                             </entry>
                         </row>
@@ -170,7 +170,7 @@
                 </tgroup>
             </informaltable>
             </para>
-            
+
             <para>
             <informaltable>
                 <tgroup cols="2">
@@ -194,39 +194,39 @@
                 </tgroup>
             </informaltable>
             </para>
-            
-        </sect2>        
-    </sect1>        
+
+        </sect2>
+    </sect1>
     <sect1 id="messages-scenarios">
         <title>Message scenarios</title>
-    
+
         <sect2 id="messages-scenarios-ct">
             <title>Compile-time weaving scenarios</title>
             <sect3 id="messages-scenarios-ct-adviceNotWoven">
                 <title>Advice not woven</title>
                 <para>This means that the pointcut for the advice did not match,
-                and it should be debugged as described in 
+                and it should be debugged as described in
                     <xref linkend="pointcuts"/>.</para>
                 </sect3>
         </sect2>
-        
+
         <sect2 id="messages-scenarios-ltw">
             <title>Load-time weaving scenarios</title>
-        
+
             <para> You can use <literal>META-INF/aop.xml</literal> to control which
             messages are produced during LTW. The following example will produce
             basic informational messages about the lifecyle of the weaver in
             addition to any warning or error messages. </para>
 
 	        <programlisting><![CDATA[
-	<aspectj>
-		<weaver options="-verbose">
-		</weaver>
-	</aspectj>
-			]]></programlisting>
-        
-            <para>The messages indicate which <literal>META-INF/aop.xml</literal> 
-            configurations file(s) are being used. Each message is also preceeded by the 
+<aspectj>
+    <weaver options="-verbose">
+    </weaver>
+</aspectj>
+]]></programlisting>
+
+            <para>The messages indicate which <literal>META-INF/aop.xml</literal>
+            configurations file(s) are being used. Each message is also preceeded by the
             name of the defining class loader associated with weaver. You can use this
             information in a large system to distinguish between different applications each
             of which will typically have its own class loader. </para>
@@ -238,25 +238,25 @@
 [AppClassLoader@92e78c] info using configuration /C:/temp/META-INF/aop-ajc.xml
 [AppClassLoader@92e78c] info register aspect ExceptionHandler
 [AppClassLoader@92e78c] info processing reweavable type ExceptionHandler: ExceptionHandler.aj
-			]]></programlisting>
-            
+]]></programlisting>
+
             <sect3 id="messages-scenarios-ltw-adviceNotWoven">
                 <title>Advice not woven</title>
         <para> It is often difficult to determine, especially when using load-time weaving (LTW),
 		why advice has not been woven. Here is a quick guide to the messages to
-		look for. Firstly if you use the <literal>-verbose</literal> option you 
+		look for. Firstly if you use the <literal>-verbose</literal> option you
 		should see the following message when your aspect is registered: </para>
 
         <programlisting><![CDATA[
-	info register aspect MyAspect
-        ]]></programlisting>
+info register aspect MyAspect
+]]></programlisting>
 
-		<para> Secondly if you use the <literal>-debug</literal> option you should 
+		<para> Secondly if you use the <literal>-debug</literal> option you should
 		see a message indicating that you class is being woven: </para>
 
         <programlisting><![CDATA[
-	debug weaving 'HelloWorld'
-        ]]></programlisting>
+debug weaving 'HelloWorld'
+]]></programlisting>
 
 		<para> However this does not mean that advice has actually been woven into
 		your class; it says that the class has been passed to the weaver. To determine
@@ -264,18 +264,18 @@
 		option which will cause a message to be issued each time a join point is woven: </para>
 
         <programlisting><![CDATA[
-	weaveinfo Join point 'method-execution(void HelloWorld.main(java.lang.String[]))' ...
-		]]></programlisting>
-        
-        <para>If advice is woven at this join point you should get the 
+weaveinfo Join point 'method-execution(void HelloWorld.main(java.lang.String[]))' ...
+]]></programlisting>
+
+        <para>If advice is woven at this join point you should get the
             corresponding message.</para>
             </sect3>
         </sect2>
     </sect1>
-            
+
     <sect1 id="messages-xlint">
         <title>Lint messages</title>
-                                <para> 
+                                <para>
                 The table below lists some useful <literal>-Xlint</literal> messages. </para>
             <informaltable>
                 <tgroup cols="3">
@@ -297,8 +297,8 @@
                             <entry>
                             	If an aspect is not being woven, despite being
                             	registered, it could be that it has been excluded
-                            	by either an <literal>include</literal> or <literal>exclude</literal> 
-                            	element in the 
+                            	by either an <literal>include</literal> or <literal>exclude</literal>
+                            	element in the
                             	<literal>aspects</literal> section of <literal>META-INF/aop.xml</literal>.
                             	Enable this message to determine whether an aspect has
                             	been excluded.
@@ -314,7 +314,7 @@
                             <entry>
                             	Issued when advice did not potentially affect any join points.
                                 This means the corresponding pointcut did not match any join
-                                points in the program.  This may be valid e.g., in library 
+                                points in the program.  This may be valid e.g., in library
                                 aspects or code picking up error conditions, but often the
                                 programmer simply made a mistake in the pointcut.  The best
                                 approach is to debug the pointcut.
@@ -356,7 +356,7 @@
                             </entry>
                             <entry>
                             	Before AspectJ 5, declare soft used to soften runtime exceptions
-                                (unnecessarily).  Since then, it does not but does issue this 
+                                (unnecessarily).  Since then, it does not but does issue this
                                 warning in case the programmer did intend for the exception
                                 to be wrapped.
                             </entry>
@@ -381,5 +381,5 @@
                 </tgroup>
             </informaltable>
     </sect1>
-   
+
 </chapter>
diff --git a/docs/pdGuideDB/trace.xml b/docs/pdGuideDB/trace.xml
index 21cc7d796..6ff915738 100644
--- a/docs/pdGuideDB/trace.xml
+++ b/docs/pdGuideDB/trace.xml
@@ -1,29 +1,29 @@
 <chapter id="trace" xreflabel="Tracing">
     <title>Tracing</title>
-    
+
     <sect1 id="trace-introduction">
         <title>Introduction</title>
-        
-        <para> 
+
+        <para>
             The AspectJ developers have instrumented the compiler/weaver with
             many "trace" messages for their own debugging use.  These remain in
-            the production releases because tracing helps when it is hard to 
+            the production releases because tracing helps when it is hard to
             isolate the problem in a test case.  This sections describes how
             to enable tracing so you can provide trace information on bug reports.
-        </para> 
-        <para> 
-            The usual approach to opening a report on Bugzilla is to describe the symptoms of the 
+        </para>
+        <para>
+            The usual approach to opening a report on Bugzilla is to describe the symptoms of the
         problem and attach a simple testcase. This allows the AspectJ team to try and reproduce the problem in
         an attempt to fix it as well as improve the test suite. Unfortunately it may not be possible
-        to produce such a testcase either because your program is too large or is commercially sensitive. Alternatively 
+        to produce such a testcase either because your program is too large or is commercially sensitive. Alternatively
         the problem may relate to your specific environment where AspectJ is being used and will not be
         reproducible by the AspectJ team. In each of these situations you can produce a
         trace of the compiler when the problem occurs instead. This can then be attached to the bug report. </para>
 
         <sect2 id="trace-configuration" xreflabel="Configuring Tracing">
             <title>Configuring Tracing</title>
-        
-            <para> When available (Java 5 or later) AspectJ will use the 
+
+            <para> When available (Java 5 or later) AspectJ will use the
             <ulink url="http://java.sun.com/j2se/1.5.0/docs/guide/logging/index.html">
             java.util.logging</ulink> infrastructure
             configured using a <literal>logging.properties</literal> file. By default only error
@@ -31,14 +31,14 @@
             method entry and exit events can be obtained using the appropriate configuration. All
             regular 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 running the AspectJ compiler/weaver under JDK 1.4 or earlier, 
+
+            <para> If you are running the AspectJ compiler/weaver under JDK 1.4 or earlier,
                 AspectJ will use a simple built-in trace
-            infrastructure that logs to stderr. This is enabled by setting the 
+            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">
@@ -73,10 +73,10 @@
                             </entry>
                             <entry>
                             	Select trace infrastructure. Specify the fully qualified class name
-                            	of the <literal>org.aspectj.weaver.tools.TraceFactory</literal> 
+                            	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. 
+                            	built-in infrastructure.
                             </entry>
                         </row>
                         <row>
@@ -97,68 +97,68 @@
 
         <sect2 id="trace-examples" xreflabel="trace-examples">
             <title>Examples</title>
-        
+
             <para> Using <literal>-Dorg.aspectj.tracing.factory=default</literal>
             	to force AspectJ to use its internal infrastructure,
-            	<literal>-Dorg.aspectj.tracing.enabled=true</literal> to turn it on and  
+            	<literal>-Dorg.aspectj.tracing.enabled=true</literal> to turn it on and
             	<literal>-Dorg.aspectj.tracing.messages=true</literal> to include messages
             	running a simple HelloWorld with LTW will generate tracing to stderr. Below
-            	is an extract from that trace with method arguments removed. 
+            	is an extract from that trace with method arguments removed.
             	You will notice the millisecond time stamp,
             	thread id and indication of entry/exit/event or message type for each line
             	of trace.
             </para>
 	        <programlisting><![CDATA[
-15:44:18.630 main > org.aspectj.weaver.loadtime.Aj.<init> 
+15:44:18.630 main > org.aspectj.weaver.loadtime.Aj.<init>
 15:44:18.660 main < org.aspectj.weaver.loadtime.Aj.<init>
 15:44:18.660 main > org.aspectj.weaver.loadtime.Aj.preProcess
 15:44:18.660 main - org.aspectj.weaver.loadtime.Aj.preProcess
 15:44:18.730 main > org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor.<init>
 15:44:18.730 main < org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor.<init>
-15:44:18.730 main > org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor.initialize 
+15:44:18.730 main > org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor.initialize
 15:44:18.821 main I [AppClassLoader@92e78c] info AspectJ Weaver Version DEVELOPMENT ...
 15:44:18.821 main > org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor.parseDefinitions
 15:44:18.821 main I [AppClassLoader@92e78c] info register classloader ...
-15:44:18.821 main - org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor.parseDefinitions 
-15:44:18.841 main - org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor.parseDefinitions 
+15:44:18.821 main - org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor.parseDefinitions
+15:44:18.841 main - org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor.parseDefinitions
 15:44:18.841 main I [AppClassLoader@92e78c] info using configuration ...
-15:44:18.891 main < org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor.parseDefinitions 
+15:44:18.891 main < org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor.parseDefinitions
 15:44:19.021 main > org.aspectj.weaver.World$TypeMap.<init>
 15:44:19.021 main < org.aspectj.weaver.World$TypeMap.<init>
 15:44:19.021 main > org.aspectj.weaver.CrosscuttingMembersSet.<init>
 15:44:19.021 main < org.aspectj.weaver.CrosscuttingMembersSet.<init>
 15:44:19.021 main > org.aspectj.weaver.Lint.<init>
 15:44:19.021 main < org.aspectj.weaver.Lint.<init>
-15:44:19.021 main > org.aspectj.weaver.World.<init> 
+15:44:19.021 main > org.aspectj.weaver.World.<init>
 15:44:19.111 main < org.aspectj.weaver.World.<init>
-15:44:19.201 main > org.aspectj.weaver.bcel.BcelWeaver.<init> 
+15:44:19.201 main > org.aspectj.weaver.bcel.BcelWeaver.<init>
 15:44:19.201 main < org.aspectj.weaver.bcel.BcelWeaver.<init>
-15:44:19.201 main > org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor.registerDefinitions 
-15:44:19.211 main > org.aspectj.weaver.bcel.BcelWeaver.setReweavableMode 
+15:44:19.201 main > org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor.registerDefinitions
+15:44:19.211 main > org.aspectj.weaver.bcel.BcelWeaver.setReweavableMode
 15:44:19.351 main < org.aspectj.weaver.bcel.BcelWeaver.setReweavableMode
-15:44:19.351 main > org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor.registerAspects 
+15:44:19.351 main > org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor.registerAspects
 15:44:19.351 main I [AppClassLoader@92e78c] info register aspect Aspect
-15:44:19.351 main > org.aspectj.weaver.bcel.BcelWeaver.addLibraryAspect 
-15:44:19.501 main - org.aspectj.weaver.bcel.BcelWorld.lookupJavaClass 
-15:44:19.632 main > org.aspectj.weaver.CrosscuttingMembersSet.addOrReplaceAspect 
-15:44:19.792 main < org.aspectj.weaver.CrosscuttingMembersSet.addOrReplaceAspect 
-15:44:19.792 main < org.aspectj.weaver.bcel.BcelWeaver.addLibraryAspect 
-15:44:19.792 main < org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor.registerAspects 
-15:44:19.792 main < org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor.registerDefinitions 
-15:44:19.792 main > org.aspectj.weaver.bcel.BcelWeaver.prepareForWeave 
+15:44:19.351 main > org.aspectj.weaver.bcel.BcelWeaver.addLibraryAspect
+15:44:19.501 main - org.aspectj.weaver.bcel.BcelWorld.lookupJavaClass
+15:44:19.632 main > org.aspectj.weaver.CrosscuttingMembersSet.addOrReplaceAspect
+15:44:19.792 main < org.aspectj.weaver.CrosscuttingMembersSet.addOrReplaceAspect
+15:44:19.792 main < org.aspectj.weaver.bcel.BcelWeaver.addLibraryAspect
+15:44:19.792 main < org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor.registerAspects
+15:44:19.792 main < org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor.registerDefinitions
+15:44:19.792 main > org.aspectj.weaver.bcel.BcelWeaver.prepareForWeave
 15:44:19.822 main < org.aspectj.weaver.bcel.BcelWeaver.prepareForWeave
 15:44:19.822 main > org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor.weaveAndDefineConcete...
 15:44:19.822 main < org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor.weaveAndDefineConcete...
-15:44:19.822 main < org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor.initialize 
-15:44:19.822 main > org.aspectj.weaver.tools.WeavingAdaptor.weaveClass 
-...            
-			]]></programlisting>
-        
+15:44:19.822 main < org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor.initialize
+15:44:19.822 main > org.aspectj.weaver.tools.WeavingAdaptor.weaveClass
+...
+]]></programlisting>
+
             <para> Alternatively when running under Java 5 the <literal>logging.properties</literal>
             	file below could be used to configure Java Logging. The resulting
-            	file, just containing trace for the 
+            	file, just containing trace for the
             	<literal>org.aspectj.weaver.loadtime</literal> package, will be
-            	written to <literal>java0.log</literal> in your <literal>user.home</literal> directory. 
+            	written to <literal>java0.log</literal> in your <literal>user.home</literal> directory.
             </para>
 
 	        <programlisting><![CDATA[
@@ -172,15 +172,15 @@ java.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatter
 java.util.logging.FileHandler.level = FINER
 
 org.aspectj.weaver.loadtime.level = FINER
-			]]></programlisting>
-        
-            <para> 
+]]></programlisting>
+
+            <para>
             	By setting the System property <literal>-Dorg.aspectj.tracing.debug=true</literal>
             	you should see a message confirming which trace infrastructure is being used.
             </para>
 	        <programlisting><![CDATA[
-	TraceFactory.instance=org.aspectj.weaver.tools.Jdk14TraceFactory@12dacd1	        
-			]]></programlisting>
+TraceFactory.instance=org.aspectj.weaver.tools.Jdk14TraceFactory@12dacd1
+]]></programlisting>
         </sect2>
     </sect1>
 </chapter>