Could not find io.netty:netty-tcnative-boringssl-static

[jamesnetherton]

azure-core depends on netty-tcnative-boringssl-static. Since the Quarkus main branch bumped to Netty 4.1.68, camel-quarkus-support-azure-core does not compile.

Seems the same issue as reported here netty/netty#11691.

Failed to execute goal on project camel-quarkus-support-azure-core: Could not resolve dependencies for project org.apache.camel.quarkus:camel-quarkus-support-azure-core:jar:2.3.0-SNAPSHOT: Could not find artifact io.netty:netty-tcnative-boringssl-static:jar:${tcnative.version} in central (https://repo.maven.apache.org/maven2) -> [Help 1]
2021-09-17T05:11:11.5234936Z org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project camel-quarkus-support-azure-core: Could not resolve dependencies for project org.apache.camel.quarkus:camel-quarkus-support-azure-core:jar:2.3.0-SNAPSHOT: Could not find artifact io.netty:netty-tcnative-boringssl-static:jar:${tcnative.version} in central (https://repo.maven.apache.org/maven2)

We should maybe investigate trying to cut out tcnative, but it leads to some native compilation issues.

[ppalaga]

This makes my parametrized BOM PR fail in Azure grouped test. The workaround on our side does not help. I filed quarkusio/quarkus#20461

[ppalaga]

We should maybe investigate trying to cut out tcnative, but it leads to some native compilation issues.

Have you tried that already? I have not realized until now that netty-tcnative / netty-tcnative-boringssl-static should not be needed with java 11 (see https://netty.io/news/2018/10/30/4-1-31-Final.html )

Regardless of that an upgrade to Netty 4.1.69.Final is now awailable in Quarkus main quarkusio/quarkus#20684

Anyway, once we have a solution for the missing tcnative version, we should also get back to having Quarkus BOM before our BOM in all CQ test modules.

[ppalaga]

Anyway, once we have a solution for the missing tcnative version, we should also get back to having Quarkus BOM before our BOM in all CQ test modules.

I have filed a separate issue for that #3222

[ppalaga]

It is more complicated than I thought in #3223 . The azure grouped test was failing in native mode.
Reverting the naive fix in #3231