Christofer Dutz

Unfortunately version 3.27.7-b1 seems to be missing the arm_64 version for linux ...

Well ... I've spent friday and saturday to prepare empty systems with: - Win x86_64 - Win amd64 - Win aarch64 - Lnx x86_64 - Lnx amd64 - Lnx aarch64...

Ok ... so on Windows in a VM on aarch64 can be convinced to work, by renaming the https://repo.maven.apache.org/maven2/com/googlecode/cmake-maven-project/cmake-binaries/3.27.7-b1/cmake-binaries-3.27.7-b1-windows-arm_64.jar Artifact to: https://repo.maven.apache.org/maven2/com/googlecode/cmake-maven-project/cmake-binaries/3.27.7-b1/cmake-binaries-3.27.7-b1-windows-arm64.jar

So I've added this to our build and it seems to be working on windows arm64 systems. Wit that I am able to build. ``` .os-windows-aarch64 windows aarch64 org.apache.maven.plugins maven-dependency-plugin...

And regarding the deployment of cmake-binaries ... wouldn't it be an option to simply re-package the files on the official cmake site? https://cmake.org/files/v3.27/

That should make things work on Windows with aarch64 cpus, a bit curious why there is no linux version for aarch64

.Well on my system Linux + aarch64 actually doesn't work, but it's a different problem I guess. Others have reported to be able to build ... I was just wondering...

Well this hack is so bad that I don't really want to put it out into the wild ;-) ... I would much more prefer to make a real solution....

Done ... see: https://github.com/asciidoctor/asciidoctor-maven-plugin/pull/350

Was able to make the hack a little cleaner, by updating to Doxia 1.8, which provides a getRelativeBaseDir method. Will now replace any occurrence of "@{project.basedir}" in any attribute value...