Bugzilla Bug 75568 : ajc changes classfile timestamps even if compilation fails (regression)
and maybe:
Bugzilla Bug 74245: -proceedOnError does not weave aspects on compile error

+ Andy using it to capture 'cant find type' issues.

	  	Weaver results in rt error if affected base class not exposed

 	wrong line for method execution join point

	  	Missing Javadoc comments that aren't missing

	  	AJC produces partial output jar file, when there are warnings during weaving
(new dependencies)

 	.lst file entries not resolved relative to list file: {boot}classpath, extdirs,

   Load Time Weaving aborts on any kind of warning (declare/xlint)

 	Weaving class loader

   Lazy instantiation of thisJoinPoint 
Speed-ups of 10-100X are measured even when running a small test case with minimal GC issues.

The actual feature implemented is that thisJoinPoint objects are only created just before calling the method for advice that requires them.  To take advantage of this feature you must use an if PCD or some other dynamic test that occurs in the PCD not the advice body to guard the expensive creation of the thisJoinPoint object.

-XlazyTjp flag must be passed to compiler to enable this feature.
If any around advice is present on the joinpoint then lazy instantiation
will be disabled.  An Xlint warning will be displayed in this case.

As a related optimization, several helper methods were added to
Factory.makeJP to reduce the code size when thisJoinPoint is used.

- 40257: parsing of "../" paths in LST files is broken 

Added interactive test for checking compiler task list messages (via browser).

The test fails so there is a bug, but in the current system we seem to use the same handler,
so the bug is harmless. (It does affect other things I'm doing.)
The test is disabled by default and can be enabled with a system property.

number of loops in BasicCommandTestCase.testSizeChanges()

   ajc needs -d . option while correctly compiling classes from subpackage

   ajc -aspectpath fails with NPE for cflow pointcuts

weave performance with and without it

for obvious forms of abstract aspects now

for obvious forms of concrete aspects, next need to address abstract