Adjust how classpath entries manipulated for Java9 support

Prior to this AspectJ would discard ignore the ClasspathEntry
objects built by JDT and just work with the classpath as a string,
driving the JDT FileSystem to rebuild classpath entries again at
a later date using the string. This is more complex in Java9 because
the string representation was losing whether some entries came in
via modulepath.  ClasspathEntry construction for modulepath entries
is non trivial (since the module-info must be processed).

The new version will cache some of the ClasspathEntry objects (those
built for modulepaths) and do more work on the AspectJ side building
classpath entries in general. It now passes these entries to a
different FileSystem entry point rather than the entry point that
takes a string path.

1 files changed, 1 insertions, 1 deletions

diff --git a/util/src/org/aspectj/util/SoftHashMap.java b/util/src/org/aspectj/util/SoftHashMap.java
index f7971bddb..94ae83441 100644
--- a/util/src/org/aspectj/util/SoftHashMap.java
+++ b/util/src/org/aspectj/util/SoftHashMap.java
@@ -12,7 +12,7 @@ import java.util.*;
 
 public class SoftHashMap<K,V> extends AbstractMap<K,V> {
 	private Map<K, SpecialValue> map;
-	private ReferenceQueue<? super V> rq = new ReferenceQueue<>();
+	private ReferenceQueue<? super V> rq = new ReferenceQueue();
 
 	public SoftHashMap() {
 		this.map = new HashMap<K,SpecialValue>();