You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then I ran mvn clean compile and encountered this error.
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 168 source files to /home/ec2-user/cello/target/classes
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 22.842 s
[INFO] Finished at: 2023-08-21T03:10:34Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile (default-compile) on project cellocad: Fatal error compiling: java.lang.IllegalAccessError: class lombok.javac.apt.Processor (in unnamed module @0x691aaaa0) 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 @0x691aaaa0 -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
I'm new to JDK/JRE and I wonder if other people have encountered the likes, and hopefully this could be resolved.
The text was updated successfully, but these errors were encountered:
Hello there,
I'm trying to compile Cello with Red Hat Enterprise Linux on AWS EC2. The dependency is first installed following INSTALL.md.
Then I ran
mvn clean compile
and encountered this error.I'm new to JDK/JRE and I wonder if other people have encountered the likes, and hopefully this could be resolved.
The text was updated successfully, but these errors were encountered: