Hello. Attempt to run a standalone app using `:run...

# jewel

[charlesmuchene]

Hello. Attempt to run a standalone app using :runReleaseDistributable fails to launch due to the following crash. Any ideas on how to resolve it?

Exception in thread "main" java.lang.IncompatibleClassChangeError: class org.jetbrains.jewel.ui.painter.SvgPainterHint cannot extend sealed interface org.jetbrains.jewel.ui.painter.PainterHint

Here’s the project: https://github.com/charlesmuchene/pref-editor-desktop

[seb]

Can you provide a bit more in terms of details and a minimal repro, and file a bug? I don't think I can go and investigate your full setup

[charlesmuchene]

The project is setup according to the Jewel read me. It’s running on:
• Compose 1.6.0-rc02
• Kotlin 1.9.21
• Gradle 8.5
• IntUI standalone 0.13.2
• JDK jbr-17 - aarch64
I have no issue running the project from the IDE.
However, executing the :runReleaseDistributable shows a bunch of warnings from proguard (missing androidx.compose.material.MaterialTheme etc) and fails the build.
Adding a proguard rule to ignore these warnings, proceeds to run the above task but fails when instantiating IntUiTheme (line 45) with

Exception in thread "main" java.lang.IncompatibleClassChangeError: class org.jetbrains.jewel.ui.painter.SvgPainterHint cannot extend sealed interface org.jetbrains.jewel.ui.painter.PainterHint

[seb]

Have you tried using the same Compose version that Jewel uses? We're not at rc2 yet

[charlesmuchene]

Yeah. I tried v1.6.0-dev1397 : same error.

[seb]

Can you please file a bug so we can track and investigate?

[HIGAN]

Can you provide a log from gradle dependencies task of your project?

[charlesmuchene]

I’ve filed a bug: https://github.com/JetBrains/jewel/issues/306

[charlesmuchene]

@HIGAN This is a sample project to repro the issue.

[HIGAN]

@charlesmuchene Try add rule

# Keep all PaintetHints
-keep interface * extends org.jetbrains.jewel.ui.painter.PainterHint

[seb]

I can confirm that disabling proguard or adding the keep rule @HIGAN suggested solves the issue. It's not a Jewel issue, it's a Proguard setup issue.

[charlesmuchene]

Thanks y’all. That resolved my issue.

[charlesmuchene]

Is there a specific criteria required to feature this project on the “Written with Jewel” 💎 readme section? cc @seb @HIGAN

[seb]

Not really, it's up to our discretion for now 🙂

[seb]

It's mostly about high quality implementations we know of, from people we know. We don't really have that much time to review submissions right now — that list is there mostly to show some real-world usages that can be taken as reference

[charlesmuchene]

Thanks for the context. Looking forward to make the cut with real-world traction.