{"agent":"claude","input":"The build fails on a newer JDK with \"java.lang.IllegalAccessError: class lombok.javac.apt.LombokProcessor cannot access class com.sun.tools.javac.processing.JavacProcessingEnvironment (in module jdk.compiler) because module jdk.compiler does not export com.sun.tools.javac.processing to unnamed module\". Find where Lombok's version is set (pom.xml properties, dependencyManagement, a parent POM, build.gradle, a version catalog) and every place the build passes flags to open JDK internals: --add-opens or --add-exports for jdk.compiler in compiler arguments, MAVEN_OPTS, .mvn/jvm.config, gradle.properties or CI files. Determine which JDKs this project is built with from the build files, toolchain config, CI workflows and Dockerfiles; if they name only an old one, also test the current long-term-support releases. Install those JDKs. On the oldest JDK that still compiles the project, build it and save the output of javap -p for every class that uses a Lombok annotation. Then raise Lombok to the newest release, build on every JDK in your list, and save the same javap output. Report a table of JDK by Lombok version with pass or the first error line. Compare the javap output before and after and list any method that appeared, disappeared or changed signature. Remove the internal-access flags you found and confirm the build still passes on every JDK without them. If the project configures annotationProcessorPaths, update Lombok's version there too. Do not change source or target levels, do not rewrite Lombok annotations by hand, and do not upgrade unrelated dependencies; list any that block the newer JDK separately. Run the test suite on each JDK. Open a pull request with the table and the comparison.","resources":[{"url":"https://github.com/your-org/your-app"}]}