Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.4.3
-
Fix Version/s: 3.0.0
-
Labels:None
Description
Given an interface such as:
public interface InvalidMethodRefExample { String getLocation(); static InvalidMethodRefExample autoDetect() { return () -> "$Default$"; } }
javac correctly produces a bootstrap method that has a MethodHandle for its second argument to LambdaMetafactory.metafactory, and the MethodHandle is to an InterfaceMethodref.
After running shade the InterfaceMethodref becomes a Methodref.
This seems to have been the result for some time now but with Java 9 it appears that the java team have decided to enforce this CP type and will be a real problem when using shade and Java 9.
Attachments
Issue Links
- is superceded by
-
MSHADE-222 Dependency updates.
-
- Resolved
-