Dmitry Shultz

@etanshaul It was not clear that Helm is not supported yet, makes sense now. I will wait for this to be supported out of the box. Thanks! ps. I'm deploying...

@etanshaul The workflow is pretty standard: 1. Use local process (TomEE in my case) to develop and test you code, but you can deploy to the cluster anytime you want...

Having this issue as well. To reproduce: 1. Checkout the [quarked-ddns](https://github.com/zeppelinux/quarked-ddns) project 2. Remove --initialize-at-runtime value in this file https://github.com/zeppelinux/quarked-ddns/blob/main/src/main/resources/application.properties 3. See native build fails with the reported exception.

I forked the io.apimatic:core and ported (tests are running from IDE but failing on some class jacoco class version) it to io.apimatic:jakarta-core:0.4.2 here https://github.com/zeppelinux/core-lib-java/tree/feature/port-to-jakarta If anybody is in the same...

I had the same issue (before facing #100). You can have a look at my pom.xml file (relevant snippet is provided in #100 as well) for a workaround that works...

Hey @franck102 there is some weirdness going on in the square pom. I spent some time trying to get to the bottom of it, but didn't solve the root cause....

@franck102 I'm glad to hear my suggestion helped! I don't see any exclusions in your snippet though... Are you sure you are not getting two okhttp jars in the classpath?

No worries @zenmasterjobo, it's all what Open Source is about, right? 🍻

Hi @franck102, the dependencyManagement exclusions work as expected as long as they applied not to import. I confirmed this by looking at the target/uarkus-app/lib. Here is the pom.xml that works...

Are they close to ship some new major version with different interface or more juice than 3.5.4? Update: Now I see they are working Java 11 compatibility and it's close...