-
-
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] lombok.config files aren't read in when compiling with sbt 1.4 #2645
Comments
Thanks for fixing this up. Can I ask if there is a release scheduled that would contain this change some time soon? |
@rzwitserloot Your fix for this issues is not complete: We ran into problems when using sbt subprojects. I provide a patch here: #2668 Please have a look (and merge 😉) before the next release, thanks! |
Any estimate when a new release will be published? This is currently blocking me from upgrading sbt 1.3.12 to 1.4.5. Thanks! |
@domdorn are you looking for an edge release or lombok v1.18.18? |
The edge release does not yet contain my fix for sbt subprojects (#2668). But it does work already for projects where Lombok is NOT used in a sub-project. |
@rzwitserloot Would be nice if you could update the edge release to latest master 😉 |
Tonight probably. |
Describe the bug
Since about sbt 1.4, there's an incremental compilation thing happening with sbt which is causing the
sourcefile
field of javac's CompilationUnits to report a virtualized URI, which lombok cannot turn into a file path, thus causing lombok to just give up on trying to find the directory to start the chain of looking forlombok.config
files.To Reproduce
Compile 'Hello, World!' in a java file with sbt while you have a
lombok.config
file present; lombok will completely ignore that config file.Additional context
The URI reported by sbt is something like
vf://tmp/$%7BBASE%7D/src/main/java/example/Main.java
See also Pull Request 2643
The text was updated successfully, but these errors were encountered: