This was required by the Eclipse team as one precondition for the next
release.

Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>

Reports common usage patterns of java.util.Map that could be replaced with Java 8 methods: getOrDefault(), computeIfAbsent(), putIfAbsent(), merge(), or replaceAll().

Signed-off-by: Lars Grefer <eclipse@larsgrefer.de>

Signed-off-by: Lars Grefer <eclipse@larsgrefer.de>

clone is saying it is protected rather than public and so we need
to add a guard to avoid creating accessor for it.

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

	  	NoSuchMethodError calling private method from around advice in inner aspect

   Advice calling protected super method causing java.lang.VerifyError 'Bad access to protected data' 
Also expanded test to cover protected field access as well as methods

Fix required getting the correct receiver type for both field access and method
calls to correspond to Java's complicated rules for accessing protected
members (JLSv2 6.6.2 and mentioned in passing in JVMv2 5.4.4)

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

default mode (inherited behaviour from JDT).

[Bug 39458] New: Compiler crash in ajc 1.1
[Bug 39460] New: Missing import crashes compiler

Bugzilla Bug 37152  
   java.lang.VerifyError:

assert or <name>.class in the body

the fix for now is just to not inline such advice, but in the future these
should be transformed to inlinable constructs

In the process of this many changes were made to try to make
keeping up with the Eclipse-JDT code base as easy as possible in
the future.

in response to tests now moved out of failing

for obvious forms of abstract aspects now

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.

clears up a huge set of warnings in Eclipse so that you
can see the wood for the trees!

this design is confiined to the aspect containing the around entirely which
makes for cleaner implementation issues and lets things like super calls
be implemented correctly.

access is made to a type not exposed to the weaver