Open Christoph460 opened 6 years ago
It is not yet not available. As far as I remember the tricky part about lombok is, that it creates getters/setters during runtime, so the information is not available for our static analyzer yet. We have to add lombok capabilities to our static analyzer to support it.
Alright, thank you your for the answer. Since our current project at Authentic Vision is mostly based on using lombok getter/setter generation during runtime, a lot of unfound messages in sourcetrail exists, which makes it under this circumstances hardly impossible to use. Looking forward when lombok will be supported.
+1
+1 via e-mail
+1
+1 via e-mail
+1
+1 getters/setters etc are created at compile time by lombok
+1
+1
+1 I just tested SourceTrail with my app (maven+lombok) - without success. However, after delombok - it was successful :-)
I had to use maven plugin that delombokifies the source, then with some help of IntelliJ - correct files that were not processed by the plugin, also I had to manually remove all @SneakyThrows and finally SourceTrail successfully scanned my code base. It's great help to learn the code base! Diagram is much better than what IntelliJ generates!
Thanks for sharing this workaround!
+1
Lombok generates the getter and setter methods during compile time, not during runtime. If Sourcetrail would be able to analyze the .class files compiled by gradle/maven it would find the methods which are missing in the .java source files.
+1
+1 , for maven
+1
+1 for maven
+1
+1
+1
+1 need it!
I would like to know if the sourcetrail (version 2018.2) supports the lombok plugin within a gradle java project.