Hi,

It should work correctly as long as you used the ‘maven-install-helper’ project with ‘mvn install’. Or alternatively use the pom file next to the jar within the ‘data’ folder i.e. the ‘mvn install’ on the ‘maven-install-helper’ folder project is configured as

...
${project.basedir}/data/prosys-opc-ua-java-sdk-codegen-maven-plugin-5.2.4-127.jar
${project.basedir}/data/prosys-opc-ua-java-sdk-codegen-maven-plugin-5.2.4-127.pom
...

(or take the pom from .m2 after the install)

Maven typically includes the pom used in the build inside the jar. In the SDK jar we have excluded that (wouldn’t work), but seems here either we forgot or that it couldn’t be easily done in a way that wouldn’t also break the plugin. We do create a “standalone” pom file as part of the build (the one next to the jar in the data folder), which is intended to be used. Lets see if we can improve this in some future version so that a “install only the jar” action would fail (or ensure the correct pom would be inside the jar).