[FEATURE] Lombok 1.18.30 still accesses JDK internal APIs

[tudousitang]

[FEATURE] Lombok 1.18.30 still accesses JDK internal APIs

[Rawi01]

No, we cannot remove the references because thats how lombok works but you can do that by setting the scope of the dependency to provided or mark the dependency as optional. (Documentation)

[rzwitserloot]

@tudousitang wrote:

Could lombok code make an enhancement to upgrade the dependencies that do not use these encapsulated JDK internal APIs? Thank you.

You're misreading the report from your tools. It's not that lombok depends on some library that then depends on javac internals. Lombok itself depends on them. No, we can't replace it with something else; if we could, we would, but despite asking, the OpenJDK team hasn't provided anything we can use. As Rawi said, your tool shouldn't be mentioning this (it's an optional dependency - at runtime lombok isn't used at all. If it compiles, you're good to go).

Shipping lombok as a thing maven understands as a compiler (where lombok-the-compiler is just a very thin wrapper that launches javac-the-compiler straight from your JDK installation, passing the appropriate --add-opens is in progress.