Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upcreate java database skip some java source file #27
Comments
|
Lombok uses non-public compiler APIs in order to achieve the modifications to compiler behaviour that it needs. In doing so, it makes assumptions that are not valid for CodeQL's Java extractor, and thus does not work with it. The recommended workaround is to delombok the code you want to analyse before running it through CodeQL. What project are you interested in? We have some (not-production-ready) experiments that may help in some cases, and it'd be interesting to try them out. |
|
hi |
|
I'm afraid I can only recommend the same workaround: delombok the code before running it through CodeQL. While, as I said, we have explored what it would take to make Lombok work natively with CodeQL, it's hard to create a maintainable solution that works across Lombok and JVM versions, and as there is a workaround the priority of doing so for us is relatively low. |
found a warn message in the log
why bypass and how to analyse
Lombok-ed source file？