Christofer Dutz

@hutcheb Can this issue be closed?

Are you using 0.12.0-SNAPSHOT or one of the last released versions? I'm asking, because a lot has changed since the last release.

I guess one of our OPC-UA folks will have to help you with that, I guess. @splatch, @hutcheb ?

Well ... guess if It's anything going wrong, we'll have to wait for a 0.12.1 or 0.13.0 for fixing it ... I'm literally doing the release right now.

Built a workaround, that uses the dependency plugin go fetch an artifact with the classifier windows-arm-64 and locally install it as windows-arm64 ... seems to make the build work.

Well it doesn#t build for me ... so we need to find out what's going on

I built the same workaround (well allmost) to the one in windows ... so I'm downloading the aarch64 binaries from the cmake site and repackaging them as jar.

So I guess, if a tag fails, you've got the configuration of your job wrong ... or is there a case where individual tags fail randomly?

Cause I think in this case the failure is coming from the PLC4X API which simply fails the entire request, if an address is wrong. So changing this for the...

Hi @takraj thanks for all the work on the OPC-UA driver you are currently working on ... highly appreciated. Could you do us a favor and sign up on our...