Skip to content
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

It can't resolve the real type of lambda when working with JRebel #50

Open
alex-lx opened this issue Mar 9, 2019 · 2 comments
Open

Comments

@alex-lx
Copy link

alex-lx commented Mar 9, 2019

It seems JRebel generated some methods on classes, and in net.jodah.typetools.TypeResolver#getMemberRef just returned JRebel's method which IMO it should be ignored.

@jhalterman
Copy link
Owner

I'm guessing the impact of this is it causes the wrong method to be matched resulting in a failed type resolution?

Happy to take a PR for this if there's a reasonably clean way of excluding JRebel methods.

@alex-lx
Copy link
Author

alex-lx commented Apr 26, 2019

Hi @jhalterman, I don't find any clear reference about what does JRebel do.
After testing on my computer, I find all JRebel's members declaring class name are starting with "com.zeroturnaround.jrebelbase.facade.". Do you think it's a reasonably clean way?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants