(similar scenario to prior, but different stack trace)

   ajc -aspectpath fails with NPE for cflow pointcuts

woven join points

- needed for release testing.

now spacewar.Game

classpath - needed for release testing

substantive changes

weave performance with and without it

   runtime NullPointerException when applying around advice to other around advice

   declare warning/error emitted without context 
and generally providing better error context information

fixed two bugs in ajcTestsFailing

for obvious forms of abstract aspects now

Bugzilla Bug 32239
Dumps assembly code if Object[] used in args (BcelRenderer.java:152)
Not surprisingly, this bug was fixed by lubbing an occurrence of ObjectType
to ReferenceType, and then dispatching back for array types and/or class
types going to BCEL.

Edit sources there and regen using the build script.

The non-.java files are resource dummies for taskdef copying tests.

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

and to add coverage for sourceroot tests

Currently showing VerifyError on recompile -- need to investigate further.

- new API to run Runnable on command completion
required to support resource-copying by ant task
during incremental compilation

Clarification on test harness vs JUnit tests.

should make incremental compilation and using binary aspect libraries
work MUCH better.
The current state doesn't fix any of those issues, but it also does
continue to pass all of the existing tests.

- removed JDK tools.jar from script classpaths
- added windowlistener to exit installer when close box clicked
- added -to {dir} option for easy GUI-free install (hack)
  due to Swing initialization, this still won't work for true
  command-line (remote, non-XWindows terminal to unix box)

   can't resolve nested public interfaces 

FIXED: Bugzilla Bug 32399  
   Incorrect binding of protected (marker) interfaces

conflicts with compiler-generated constructor

   ajc reports error when encountering static declaration of nested classes

   Negation of if pointcut does not work

matching kinds with SignaturePattern

-- this bug was found by the unit tests and should have been fixed when
   this method was added

This adds an optional "context" String to IMessage.
The IMessage creator should create a context String (or use an implementation that lazily creates one).
The IMessage client can render their messages without context embedded in the message field.

Emitting source context from the weaver will be harder.
Using file and start/end line will probably work, since tool clients can map to any available source file paths.
(BcelSourceContext and BcelShadow can be updated with end from range.)