Problem has been solved after upgrading the Maven wrapper. Now GitHub Actions can issue a successful "./mvnw verify" for both master and release-2.x branches! 🥳 🎉
Even though "verify" succeeds, for some reason test reports still point to certain errors. See the latest successful builds on master <https://github.com/apache/logging-log4j2/actions/runs/223292206> and release-2.x <https://github.com/apache/logging-log4j2/actions/runs/223441220> branches. I will try to spend time fixing them. That said, I will really appreciate it if you can skim through the failures and see if it rings any bells for you. On Fri, Aug 21, 2020 at 11:31 AM Volkan Yazıcı <volkan.yaz...@gmail.com> wrote: > GitHub Actions CI build is failing on release-2.x > <https://github.com/apache/logging-log4j2/runs/1008091524> with the > following error: > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-toolchains-plugin:1.1:toolchain (default) on > project log4j-api-java9: Misconfigured toolchains. Non-existing JDK home > configuration at > /Users/runner/work/logging-log4j2/logging-log4j2/${env.JAVA_HOME_8_X64} -> > [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-toolchains-plugin:1.1:toolchain > (default) on project log4j-api-java9: Misconfigured toolchains. > > I am confused and clueless, since the very same [GitHub Actions] > configuration works perfectly well on "master". Any ideas? Matt? >
