-
Notifications
You must be signed in to change notification settings - Fork 227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backporting a method reference to interface enum methods fails #69
Comments
Thanks. I've located that the thing which triggers this bug is |
@orfjackal thank you. One more question please: would it be possible to mention problematic classes like |
Error reporting improved. Earlier it reported only problematic lambda classes. Now it reports all classes. |
@orfjackal this is great, thank you! :) |
And now it reports also the lambda/method reference which caused the problem. :) |
The improved error messages is included in Retrolambda 2.1.0. The fix for this issue is still under work. |
Hi,
Please consider the following code. A simple interface that associates a parameterized key with an object:
A special test enum whose members are associated with a key:
An utility method that builds an
IIdentifiable
-enum index using Google Guava:Please note that the last method lambda can be simplified to a method reference like this:
Once this refactoring is performed, the Retrolambda (I'm using the Maven plugin) is not able to backport the method reference producing the following error during the build:
My JDK version is 1.8.0.40 (64). Could you please check? Thanks!
(Also it was difficult to find out which class fails. Is it possible to configure the Retrolambda Maven plugin to report which classes and methods fail to be backported? Currently the plugin only reports the previously saved lambdas like
Saving lambda class: foo/bar/Baz$$Lambda$1
, and I couldn't find the failed classes even with the Maven option-X
set on.)The text was updated successfully, but these errors were encountered: