Kura Build 5.4.0 RELEASE FAIL for profiles raspberry-pi-arm64 & raspberry-pi-arm64-nn with JAVA 17

[alexcorvis84]

Hi,

I'm trying to build the Kura 5.4.0 version from latest tag for the profiles raspberry-pi-arm64 & raspberry-pi-arm64-nn with JAVA 17 and I'm getting the following error which stops the compiling process:

I'm using the ./build-menu.sh script available and selecting raspberry-pi-arm64, raspberry-pi-arm64-nn, Java 17 profiles. I'm performing the build process inside a Docker container with the image maven:3.8.5-openjdk-17.

Any help is welcome!

Thanks in advance.

[marcellorinaldo]

Hi,

I'm trying to build the Kura 5.4.0 version from latest tag for the profiles raspberry-pi-arm64 & raspberry-pi-arm64-nn with JAVA 17 and I'm getting the following error which stops the compiling process:

I'm using the ./build-menu.sh script available and selecting raspberry-pi-arm64, raspberry-pi-arm64-nn, Java 17 profiles. I'm performing the build process inside a Docker container with the image maven:3.8.5-openjdk-17.

Any help is welcome!

Thanks in advance.

Hi @alexcorvis84. Currently to build Kura on a machine with JRE 17 you should use the maven profile -Pjava17, so that it will not compile bundles that are not compatbile with that Java version and adjust the test environment accordingly. I have not much experience with the ./build-menu.sh script, but I think that it does not take the new flag into account.

Here some references to the relevant maven builds for building on Java 17 for target Java 17:

• target platform
• kura main
• distrib

[alexcorvis84]

See below screenshot as evidence

[marcellorinaldo]

I see that it fails on the features build. In the image it fails when trying to get the dependencies for creating the script filter DP, which is skipped on a Java 17 build.

Unfourtunately, even excluding the script filter project it will fail on a later stage when producing the DP with the osgi-dp plugin. The osgi-dp plugin is compatible only with Java 8.

We discussed the update of it but the lack of expertise in Maven plugin development kept us postponing that issue.

This is the link to the osgi-dp plugin:
https://github.com/ctron/osgi-dp

[alexcorvis84]

Hi @marcellorinaldo, if I try to build 5.3.0 RELEASE with the same method exposed, it works and I can get the binaries built, but with 5.4.0 RELEASE I got the error shared.

Is this the expected behaviour with 5.4.0 Release? I expected the same output as previous version... 🤔

[marcellorinaldo]

Inspecting closely, this commit might have broken the tests on java 17 by requiring the wire.script.filter dependency in the tests pom

• code point: https://github.com/eclipse/kura/blame/d26bca6c654a3285447b21eb979f26e28584244b/kura/test/org.eclipse.kura.rest.packages.provider.test/pom.xml#L427C15-L427C15
• git blame: d74484b#diff-2ff5cbda7768db952d3525d7213b9350acee6699ec729ceb29595e5c5bfe3119

[mattdibi]

Ouff... my bad. I probably copy-pasted the integration tests from another bundle for starting out without checking. Obviously the integration tests for the rest.packages do not need the wire.script.filter. It didn't came out earlier because my toolchain (and the CI ones) are still Java8 based.

@alexcorvis84 We'll obviously need to fix this but as workaround I think that you can:

• Do not build the tests (-Dmaven.test.skip=true), I think this should work (hopefully)
• Switch to Java 8 for building.

[alexcorvis84]

Ouff... my bad. I probably copy-pasted the integration tests from another bundle for starting out without checking. Obviously the integration tests for the rest.packages do not need the wire.script.filter. It didn't came out earlier because my toolchain (and the CI ones) are still Java8 based.

@alexcorvis84 We'll obviously need to fix this but as workaround I think that you can:

* Do not build the tests (`-Dmaven.test.skip=true`), I think this should work (hopefully)

* Switch to Java 8 for building.

Hi @mattdibi , build has worked with the two amends provided 👍🏼 Thanks for your suggestions!

Anyway, I'll stay tuned for your news, hoping JAVA17 build gets fixed as soon as possible.

Many thanks in advance. Regards.

[mattdibi]

Fixed in #5117. @alexcorvis84 feel free to reopen this if you encounter issues with the fix.