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

Lombok nullpointer in PatchDelegate in Eclipse Mars #913

Closed
kristjant opened this issue Sep 7, 2015 · 6 comments
Closed

Lombok nullpointer in PatchDelegate in Eclipse Mars #913

kristjant opened this issue Sep 7, 2015 · 6 comments

Comments

@kristjant
Copy link

I'm using Eclipse Mars with Lombok 1.16.6 and lombok throws the following exception when compiling:

Internal compiler error: java.lang.NullPointerException at lombok.eclipse.agent.PatchDelegate.addAllMethodBindings0(PatchDelegate.java:702)
Foo.java /project/src/foo/line 0 Java Problem

binding.scope is null there and because of that Eclipse throws a nullpointer from lombok when compiling.

@rspilker
Copy link
Collaborator

Can you back up the claim that on that line ((SourceTypeBinding) binding).scope is null? The constructor would not have completed for a null scope, and I could not find any evidence that it is set to null later.

@hnadra
Copy link

hnadra commented Jan 26, 2016

I'm getting the same issue. I put a breakpoint and I can see scope is null. The binding is a SourceBinding for a class that is used as a delegate from another class. The stack of the JVM is attached.
stack.txt

@rspilker
Copy link
Collaborator

rspilker commented Jun 27, 2016

I've added a fix, but have not been able to reproduce the problem myself. Can someone give the latest edge release a try?

rspilker added a commit that referenced this issue Jun 28, 2016
@rspilker
Copy link
Collaborator

I've update the edge release, can someone give it a try?

@hnadra
Copy link

hnadra commented Jul 11, 2016

I tested with the edge release and didn't see the error. I also confirmed that the error was occurring with the 1.16.8 release which doesn't include this fix.

@rspilker
Copy link
Collaborator

rspilker commented Jul 12, 2016

Thanks for the confirmation. We'll probably ship a new version this week.

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

3 participants