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

	  	NPE on thisJoinPoint mistake

 	declare soft can cause programs with invalid exception behaviour to be generated

	  	AspectJ does not correctly support -cp

	  	Avoid clashes in the org.eclipse namespace by renaming our duplicates.

	  	Bootclasspath specification for compiling is not possible

	  	Bogus error message: The abstract method ajc$pointcut$$tracingScope$a2 in type Tracing can only be defined by an abstract class

+ 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

new relationships (such as the example in the sandbox that adds additional
declared-parents relationships).  There is no structural change to the compiler
or weaver.  The AsmRelationshipProvider is now accessed by getDefault()
instead of statically, and its instance can be reset to be a subtype.

	  	Missing Javadoc comments that aren't missing

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

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

	  	NoSuchMethodError calling private method from around advice in inner aspect

	  	intertype initialisers should match field set pointcuts

 	proceed used as method name in around advice

adding better message to the assert so we can hopefully find out why
the build machine is getting upset.

test case constants (not added by me may I add ;) ). Since I was developing
on Linux, I didn't catch it.