Better binary compatibility for advice method names 
- I've run the tests a thousand times and they all pass, I'm still nervous about this first big commit though *gulp*

When creating obj thru intro constructor init code fails to execute

effect of an after returning type incompatible with a join point return type

effect of an after returning type incompatible with a join point return type

effect of an after returning type incompatible with a join point return type

LocalVariableTable sometimes gets BCEL-supplied parameter names

LocalVariableTable sometimes gets BCEL-supplied parameter names

this is now a patched version of bcel-5.1 -- it was
previously an unpatched version of bcel-5.0.

   CatchClauseSignature has broken operation

   duplicate warning or second join point for constructor-execution

this is a long-standing bug that was masked by the weaver which
would always recompute this field.  optimizations to the weaver made
this bug appear again.

   Better binary compatibility for advice method names

   Better binary compatibility for advice method names

 	Make a full implementation of org.eclipse.jdt.core for use in AJDT
Pushdown of AjParser and AjScanner into shadows/org.eclipse.jdt.core.
New class DeclarationFactory handles creation of AJDT-specific types
on behalf of Parser.

 	Make a full implementation of org.eclipse.jdt.core for use in AJDT
Updated jdtcore jars, and an external builder configured in build
chain to refresh them from the shadows...

shadows/org.eclipse.jdt.core in your workspace (which will be 
most of the time), this dummy project will satisfy the
build dependency of the HEAD org.eclipse.jdt.core project.

   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.

into this source - only the org.eclipse.jdt.core project should
contain links to other portions of eclipse source.

removed unused imports, local variables, and private methods
(still there, just commented out).

removed unused imports, local variables, and private methods
(still there, just commented out).

removed unused imports, local variables, and private methods
(still there, just commented out).

removed unused imports, local variables, and private methods
(still there, just commented out).

removed unused imports, local variables, and private methods
(still there, just commented out).

removed unused imports, local variables, and private methods
(still there, just commented out).

removed unused imports, local variables, and private methods
(still there, just commented out).

   aspectjrt.jar manifest file name needs changing to upper case