-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[BUG] Maven + Java 11 + Lombok 1.18.8 + package-info.java without "package ..." -> NullPointerException #2184
Comments
Maybe this is related: #2183 |
Just to be certain, the problem does not occur if you remove your lombok dependency? |
rspilker
added
the
parked
Without further feedback this bug cannot be processed. If no feedback is provided, we close these.
label
Jul 24, 2019
no it doesnt try it in the project i set up |
thanks for the fast response! I will check it out. Just so you know, we have many reports and only limited time, so before we pull and compile, we want to make sure there is a real problem. |
I could also reproduce this problem without using mvn:
|
rspilker
removed
the
parked
Without further feedback this bug cannot be processed. If no feedback is provided, we close these.
label
Jul 24, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When using Java 11 and maven and lombok and when you have a package-info.java somewhere that does not have a package statement, the compiler generates an NPE.
To Reproduce
Clone and follow the instructions:
https://github.com/Masterxilo/javac-11-mvn-bug-lombok-packageinfo-bug
mvn clean compile
Observed behaviour
or more precisely
Expected behavior
Should compile just fine.
OR
Should report the "errror" of not having a package specified clearly.
Workaround/Hackfix
Make sure all package-info.java files have a valid package statement.
Version info (please complete the following information):
Additional context
If you are on windows, you can enable java 11 like this i it is installed:
The text was updated successfully, but these errors were encountered: