[aspectj-dev] AspectJ compiler moved to Eclipse 3.0 M6 JDT base

[Adrian Colyer <adrian_colyer@xxxxxxxxxx>]

Some of you may have noticed a larger-than-usual
commit to the CVS tree earlier today. Jim and I - that's mostly Jim with
me playing assistant - committed the update that moves the org.eclipse.jdt.core
in the aspectj distribution up to the 3.0 M6 JDT compiler level. This will
have to be updated once more when 3.0 becomes final, but we believe the
bulk of the work has been done to make this next update more palatable
when the time comes. As well as picking up all the fixes (and any new bugs)
introduced into the jdt compiler in the 3.0 stream, this change also picks
up a significant change in the default behaviour of the eclipse java compiler
:- the default compilation mode is now 1.4 compliance. The byte codes generated
in 1.4 compliant mode preserve the static type of the receiver in a call,
rather than replacing with the root defining type as happens under 1.3.
The change in behaviour flushed out a few additional bugs in AspectJ which
have also been fixed and the test cases updated. 

The readme-1.2 file has yet to be updated
(created) to document the change in default compliance level. The change
will work hand-in-hand with the enhancement committed into the tree last
week to warn (Xlint) when a declaring type pattern is used in a call pcd
in such a way that likely desired matches are excluded.

-- Adrian
Adrian_Colyer@xxxxxxxxxx