@erizzo do you also experience the following?

[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR : 
[INFO] -------------------------------------------------------------
[ERROR] /home/runner/work/assertj/assertj/assertj-core/src/main/java/module-info.java:[55,19] net.bytebuddy cannot be resolved to a module
[INFO] 1 error
[INFO] -------------------------------------------------------------

@erizzo do you also experience the following?

[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR : 
[INFO] -------------------------------------------------------------
[ERROR] /home/runner/work/assertj/assertj/assertj-core/src/main/java/module-info.java:[55,19] net.bytebuddy cannot be resolved to a module
[INFO] 1 error
[INFO] -------------------------------------------------------------

Do you mean with this branch or on main?
I've not seen that on main.

Do you mean with this branch or on main?

There shouldn't be changes from this branch that would cause it, it should be practically equivalent to main. In the end, I'm trying to compile things using the maven-compiler-plugin configuration, which might differ from what Eclipse does natively.

Thanks for the feedback, I'll dig a bit more!

[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR : 
[INFO] -------------------------------------------------------------
[ERROR] /home/runner/work/assertj/assertj/assertj-core/src/main/java/module-info.java:[55,19] net.bytebuddy cannot be resolved to a module
[INFO] 1 error
[INFO] -------------------------------------------------------------

Hi @raphw, are you aware of any incompatibilities between ByteBuddy and ECJ?

Could the error above be related to the fact that ByteBuddy has the module descriptor under META-INF/versions/9?

Obviously, I found a related issue right after submitting this comment 🙃

• ECJ batch compiler only loads multi-release classes with exact --release match eclipse-jdt/eclipse.jdt.core#2778

If so, this would fail for a range of libraries. I know of Byte Buddy being used as a module, so I'd be surprised of an error in the jar.

So far, I can't find anything unusual in our build that would cause such an error.

I'll cherry-pick the other fixes, but the current error with ByteBuddy prevents us from merging this job.

If anyone has any ideas, please feel free to chime in!