Fix for e43 build

groovy · Jul 4, 2017 · 40d8184 · 40d8184
1 parent 4b2402f
commit 40d8184
Show file tree

Hide file tree

Showing 3 changed files with 15 additions and 3 deletions.
diff --git a/...eclipse.jdt.core/compiler/org/eclipse/jdt/internal/compiler/lookup/SourceTypeBinding.java b/...eclipse.jdt.core/compiler/org/eclipse/jdt/internal/compiler/lookup/SourceTypeBinding.java
@@ -971,11 +971,15 @@ public FieldBinding getField(char[] fieldName, boolean needResolve) {
 	return null;
 }
 
-// GROOVY start
+// GROOVY add
 // FIXASC (M3) is this the right approach to adding extra methods? Probably not - they should be forced on when created
 public MethodBinding[] getAnyExtraMethods(char[] selector, TypeBinding[] argumentTypes) {
 	return (this.scope == null ? null : this.scope.getAnyExtraMethods(selector, argumentTypes));
 }
+
+public boolean isPrototype() {
+	return true;
+}
 // GROOVY end
 
 // NOTE: the return type, arg & exception types of each method of a source type are resolved when needed

diff --git a/...eclipse.jdt.core/compiler/org/eclipse/jdt/internal/compiler/lookup/SourceTypeBinding.java b/...eclipse.jdt.core/compiler/org/eclipse/jdt/internal/compiler/lookup/SourceTypeBinding.java
@@ -986,11 +986,15 @@ public FieldBinding getField(char[] fieldName, boolean needResolve) {
 	return null;
 }
 
-// GROOVY start
+// GROOVY add
 // FIXASC (M3) is this the right approach to adding extra methods? Probably not - they should be forced on when created
 public MethodBinding[] getAnyExtraMethods(char[] selector, TypeBinding[] argumentTypes) {
 	return (this.scope==null?null:this.scope.getAnyExtraMethods(selector, argumentTypes));
 }
+
+public boolean isPrototype() {
+	return true;
+}
 // GROOVY end
 
 // NOTE: the return type, arg & exception types of each method of a source type are resolved when needed

diff --git a/...eclipse.jdt.core/compiler/org/eclipse/jdt/internal/compiler/lookup/SourceTypeBinding.java b/...eclipse.jdt.core/compiler/org/eclipse/jdt/internal/compiler/lookup/SourceTypeBinding.java
@@ -990,11 +990,15 @@ public FieldBinding getField(char[] fieldName, boolean needResolve) {
 	return null;
 }
 
-// GROOVY start
+// GROOVY add
 // FIXASC (M3) is this the right approach to adding extra methods? Probably not - they should be forced on when created
 public MethodBinding[] getAnyExtraMethods(char[] selector, TypeBinding[] argumentTypes) {
 	return (this.scope==null?null:this.scope.getAnyExtraMethods(selector, argumentTypes));
 }
+
+public boolean isPrototype() {
+	return true;
+}
 // GROOVY end
 
 // NOTE: the return type, arg & exception types of each method of a source type are resolved when needed