Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
21 commits
Select commit Hold shift + click to select a range
01f50e9
Chore: Move the Compose fork pin to 1.11.1-ext.2
b-re-w Oct 25, 2026
c6c8d43
Fix: Publish the scene for macosArm64 with the window modules and fol…
b-re-w Oct 25, 2026
27d848f
Fix: Feed the fork's X11 windows their accessibility tree through Sce…
b-re-w Oct 25, 2026
f04066f
Fix: Ask for the skiko-awt the pinned fork publishes
b-re-w Oct 25, 2026
bf03e00
Fix: Upload the fork modules from one root so the download keeps org/…
b-re-w Oct 25, 2026
2d0473d
Fix: Keep the fork modules artifact rooted at org with a marker file
b-re-w Oct 25, 2026
3e26d02
Fix: Let Amper take the fork's skiko-awt and keep JetBrains' off the …
b-re-w Oct 25, 2026
56eba4f
Revert "Fix: Let Amper take the fork's skiko-awt and keep JetBrains' …
b-re-w Oct 25, 2026
af42fde
Chore: Pin the window modules to the fork's extended head (WIP)
b-re-w Oct 26, 2026
8fbcf86
Feat: Hand the scene's semantics to the fork windows' own accessibili…
b-re-w Oct 26, 2026
3589142
Chore: Pin the window modules to the fork's extended head with #170 m…
b-re-w Oct 26, 2026
b7ebbcb
Chore: Adopt the fork's 1.11.1-ext.2 coordinates with all three pins …
b-re-w Oct 26, 2026
35648fc
Fix: Publish mingwX64 through the fork's publish-local.sh under the f…
b-re-w Oct 26, 2026
3aa3940
Fix: Take skiko-awt at the fork's group for Amper, publish scene with…
b-re-w Oct 26, 2026
265b929
Docs: Link the follow-up that restores the Compose build comparison
b-re-w Oct 26, 2026
86afecc
Fix: Answer the fork wrappers' names the other desktops declare so ea…
b-re-w Oct 26, 2026
49bcdb9
Fix: Redraw the macOS window when the Host asks for a frame so the fo…
b-re-w Oct 26, 2026
a1ed662
Fix: Link the fork's compiled-in ICU data object in the Windows stati…
b-re-w Oct 26, 2026
3959eb2
Merge remote-tracking branch 'origin/fix/repin-macos-kn-frames' into …
b-re-w Oct 26, 2026
efe0736
Fix: Carry the fork's compiled-in ICU object in the Windows kit
b-re-w Oct 26, 2026
82399ea
Chore: Pin the fork at the merge of the macOS event-drag metrics (#173)
b-re-w Oct 26, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion .github/workflows/fork-desktop-modules.yml
Original file line number Diff line number Diff line change
Expand Up @@ -70,11 +70,18 @@ jobs:
./scripts/publish-skiko-awt.sh "$RUNNER_TEMP/skiko-awt"
find ~/.m2/repository/org/thisisthepy/compose -name '*.jar' | sort

- name: Mark the artifact root
# upload-artifact roots the artifact at the common parent of its paths. skiko-awt now
# sits inside org/thisisthepy/compose, so this marker keeps the root at org, and the
# download into ~/.m2/repository/org restores the org/thisisthepy/compose prefix.
run: touch ~/.m2/repository/org/.compose-fork-desktop

- name: Keep the published modules
uses: actions/upload-artifact@v4
with:
name: compose-fork-desktop
include-hidden-files: true
path: |
~/.m2/repository/org/thisisthepy/compose
~/.m2/repository/org/jetbrains/skiko/skiko-awt
~/.m2/repository/org/.compose-fork-desktop
retention-days: 7
11 changes: 8 additions & 3 deletions .github/workflows/test-compose-from-fork.yml
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@
# differs between the two;
# 3. the two repositories are compared file by file, and every archive entry by entry with
# zip timestamps left out (.github/scripts/compare-maven-repos.py). The fork publishes
# under its own coordinates (org.thisisthepy.compose at 1.11.1-ext.1) where the old build
# under its own coordinates (org.thisisthepy.compose at 1.11.1-ext.2) where the old build
# used JetBrains' (org.jetbrains.compose at 1.11.1), so the fork's side is read under the
# old names: its paths, its metadata and the module names inside its klibs. It also
# publishes every sibling its modules name, which the old build took from JetBrains, so
Expand Down Expand Up @@ -315,6 +315,11 @@ jobs:
# The comparison runs before the renderer and does not stop it, so that one failing
# does not hide the other's result. This is where a difference fails the job.
if: always() && steps.compare.outcome == 'failure'
# The comparison proved the fork equals the old patched build while the pin was the
# commit that held the same tree. The pin has moved on to the fork's ext.2 line, whose
# Compose differs on purpose (new metadata, new sources), so a difference is reported
# in the comparison step and no longer fails the job. The renderer built against the
# fork's publication below is the proof that matters now. The guard is to come back as a
# comparison with the ext.2 baseline: DarkPyonix/compose-rust#361.
run: |
echo "the fork and the patched build published different contents; see the comparison step" >&2
exit 1
echo "the fork and the patched build published different contents, as the moved pin is expected to; see the comparison step" >&2
9 changes: 8 additions & 1 deletion .github/workflows/test-graalvm-renderer.yml
Original file line number Diff line number Diff line change
Expand Up @@ -283,13 +283,20 @@ jobs:
./scripts/publish-skiko-awt.sh "$RUNNER_TEMP/skiko-awt"
find ~/.m2/repository/org/thisisthepy/compose -name '*.jar' | sort

- name: Mark the artifact root
# upload-artifact roots the artifact at the common parent of its paths. skiko-awt now
# sits inside org/thisisthepy/compose, so this marker keeps the root at org, and the
# download into ~/.m2/repository/org restores the org/thisisthepy/compose prefix.
run: touch ~/.m2/repository/org/.compose-fork-desktop

- name: Keep the published modules
uses: actions/upload-artifact@v4
with:
name: compose-fork-desktop
include-hidden-files: true
path: |
~/.m2/repository/org/thisisthepy/compose
~/.m2/repository/org/jetbrains/skiko/skiko-awt
~/.m2/repository/org/.compose-fork-desktop
retention-days: 7

linux-x64:
Expand Down
8 changes: 4 additions & 4 deletions .github/workflows/test-windows-resize-metrics.yml
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@ jobs:
~/.m2/repository
.scratch/skiko-build/out/windows-x64/skiko-bridges.lib
.scratch/skiko-build/out/windows-x64/skia
.scratch/skiko-build/out/windows-x64/embedded_icu.cpp
.scratch/skiko-build/out/windows-x64/embedded_icu.obj
key: compose-mingwx64-${{ hashFiles('renderer/scripts/build-compose.sh', 'renderer/scripts/compose-fork-mingw.changes') }}

- name: Make room for the Compose build
Expand Down Expand Up @@ -120,7 +120,7 @@ jobs:
~/.m2/repository
.scratch/skiko-build/out/windows-x64/skiko-bridges.lib
.scratch/skiko-build/out/windows-x64/skia
.scratch/skiko-build/out/windows-x64/embedded_icu.cpp
.scratch/skiko-build/out/windows-x64/embedded_icu.obj
key: ${{ steps.kit-cache.outputs.cache-primary-key }}

- name: Report what was published
Expand All @@ -141,7 +141,7 @@ jobs:
~/.m2/repository
.scratch/skiko-build/out/windows-x64/skiko-bridges.lib
.scratch/skiko-build/out/windows-x64/skia
.scratch/skiko-build/out/windows-x64/embedded_icu.cpp
.scratch/skiko-build/out/windows-x64/embedded_icu.obj
if-no-files-found: error
retention-days: 3

Expand Down Expand Up @@ -199,7 +199,7 @@ jobs:
rm -rf ~/.m2/repository .scratch/skiko-build/out/windows-x64
mv "$m2" ~/.m2/repository
mv "$skiko" .scratch/skiko-build/out/windows-x64
ls ~/.m2/repository/org/jetbrains/compose/ui | head
ls ~/.m2/repository/org/thisisthepy/compose/ui | head
ls -la .scratch/skiko-build/out/windows-x64

- name: Restore the Kotlin toolchain
Expand Down
8 changes: 4 additions & 4 deletions .github/workflows/windows-static.yml
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ jobs:
~/.m2/repository
.scratch/skiko-build/out/windows-x64/skiko-bridges.lib
.scratch/skiko-build/out/windows-x64/skia
.scratch/skiko-build/out/windows-x64/embedded_icu.cpp
.scratch/skiko-build/out/windows-x64/embedded_icu.obj
key: compose-mingwx64-${{ hashFiles('renderer/scripts/build-compose.sh', 'renderer/scripts/compose-fork-mingw.changes') }}

- name: Make room for the Compose build
Expand Down Expand Up @@ -110,7 +110,7 @@ jobs:
~/.m2/repository
.scratch/skiko-build/out/windows-x64/skiko-bridges.lib
.scratch/skiko-build/out/windows-x64/skia
.scratch/skiko-build/out/windows-x64/embedded_icu.cpp
.scratch/skiko-build/out/windows-x64/embedded_icu.obj
key: ${{ steps.kit-cache.outputs.cache-primary-key }}

- name: Report what was published
Expand All @@ -131,7 +131,7 @@ jobs:
~/.m2/repository
.scratch/skiko-build/out/windows-x64/skiko-bridges.lib
.scratch/skiko-build/out/windows-x64/skia
.scratch/skiko-build/out/windows-x64/embedded_icu.cpp
.scratch/skiko-build/out/windows-x64/embedded_icu.obj
if-no-files-found: error
retention-days: 3

Expand Down Expand Up @@ -189,7 +189,7 @@ jobs:
rm -rf ~/.m2/repository .scratch/skiko-build/out/windows-x64
mv "$m2" ~/.m2/repository
mv "$skiko" .scratch/skiko-build/out/windows-x64
ls ~/.m2/repository/org/jetbrains/compose/ui | head
ls ~/.m2/repository/org/thisisthepy/compose/ui | head
ls -la .scratch/skiko-build/out/windows-x64

- name: Restore the Kotlin toolchain
Expand Down
10 changes: 5 additions & 5 deletions docs/guide/en/troubleshooting.html
Original file line number Diff line number Diff line change
Expand Up @@ -119,7 +119,7 @@ <h2 id="fork-artifacts">The build stops: the fork's artifacts are missing</h2>
<p>
The renderer depends on modules only the Compose fork publishes, and only into
<code>~/.m2</code>: the patched Compose under its own group and version
(<code>org.thisisthepy.compose.*</code>, <code>1.11.1-ext.1</code>), skiko-awt under
(<code>org.thisisthepy.compose.*</code>, <code>1.11.1-ext.2</code>), skiko-awt under
<code>0.144.6.1</code>, the Linux targets, and the window modules. Every
renderer script checks for them before the Kotlin toolchain runs and stops like this:
</p>
Expand All @@ -128,7 +128,7 @@ <h2 id="fork-artifacts">The build stops: the fork's artifacts are missing</h2>
<pre><code>error: the Compose fork's artifacts are not in the local Maven repository
...
missing, under ~/.m2/repository:
org/thisisthepy/compose/foundation/foundation/1.11.1-ext.1/foundation-1.11.1-ext.1.pom
org/thisisthepy/compose/foundation/foundation/1.11.1-ext.2/foundation-1.11.1-ext.2.pom
fix, from the repository root, then run this build again:
renderer/scripts/build-compose.sh --target macosArm64</code></pre>
</figure>
Expand All @@ -140,7 +140,7 @@ <h2 id="fork-artifacts">The build stops: the fork's artifacts are missing</h2>
<p>
The check also reads the metadata the fork published. Every module the fork's metadata names
under <code>org.thisisthepy.compose</code> has to be published too, for each target the
renderer builds, or <code>foundation 1.11.1-ext.1</code> asks for a sibling that exists
renderer builds, or <code>foundation 1.11.1-ext.2</code> asks for a sibling that exists
nowhere. <code>renderer/scripts/fork-dependencies.sh check</code> lists any that are
missing. If it lists some, run <code>build-compose.sh</code> again, which publishes the
fork's whole set.
Expand All @@ -152,8 +152,8 @@ <h2 id="stale-state">The fork is published and resolution still fails</h2>
</p>
<figure class="codeblock">
<figcaption>output</figcaption>
<pre><code>ERROR: Unable to resolve dependency org.thisisthepy.compose.foundation:foundation:1.11.1-ext.1
Unable to download checksums of file foundation-1.11.1-ext.1.pom</code></pre>
<pre><code>ERROR: Unable to resolve dependency org.thisisthepy.compose.foundation:foundation:1.11.1-ext.2
Unable to download checksums of file foundation-1.11.1-ext.2.pom</code></pre>
</figure>
<p>
The cause is the Kotlin toolchain's incremental state. A build that ran before the fork was
Expand Down
10 changes: 5 additions & 5 deletions docs/guide/ko/troubleshooting.html
Original file line number Diff line number Diff line change
Expand Up @@ -115,7 +115,7 @@ <h2 id="no-window">빌드되고 실행되는데 창이 뜨지 않습니다</h2>
<h2 id="fork-artifacts">빌드가 멈춥니다: 포크의 아티팩트가 없습니다</h2>
<p>
렌더러는 Compose 포크만 게시하는 모듈에 기대고, 포크는 그것을 <code>~/.m2</code> 에만
게시합니다. 자기 그룹과 버전(<code>org.thisisthepy.compose.*</code>, <code>1.11.1-ext.1</code>)으로
게시합니다. 자기 그룹과 버전(<code>org.thisisthepy.compose.*</code>, <code>1.11.1-ext.2</code>)으로
낸 패치된 Compose, <code>0.144.6.1</code> 의 skiko-awt, Linux 타깃, 창 모듈입니다. 렌더러 스크립트는 모두 Kotlin 툴체인을 돌리기 전에 이것을
확인하고, 없으면 이렇게 멈춥니다.
</p>
Expand All @@ -124,7 +124,7 @@ <h2 id="fork-artifacts">빌드가 멈춥니다: 포크의 아티팩트가 없습
<pre><code>error: the Compose fork's artifacts are not in the local Maven repository
...
missing, under ~/.m2/repository:
org/thisisthepy/compose/foundation/foundation/1.11.1-ext.1/foundation-1.11.1-ext.1.pom
org/thisisthepy/compose/foundation/foundation/1.11.1-ext.2/foundation-1.11.1-ext.2.pom
fix, from the repository root, then run this build again:
renderer/scripts/build-compose.sh --target macosArm64</code></pre>
</figure>
Expand All @@ -135,7 +135,7 @@ <h2 id="fork-artifacts">빌드가 멈춥니다: 포크의 아티팩트가 없습
<p>
이 확인은 포크가 게시한 메타데이터도 읽습니다. 포크의 메타데이터가
<code>org.thisisthepy.compose</code> 아래에서 부르는 모듈은 렌더러가 빌드하는 타깃마다 모두
게시되어 있어야 합니다. 그렇지 않으면 <code>foundation 1.11.1-ext.1</code> 이 어디에도 없는 형제
게시되어 있어야 합니다. 그렇지 않으면 <code>foundation 1.11.1-ext.2</code> 이 어디에도 없는 형제
모듈을 요구합니다. <code>renderer/scripts/fork-dependencies.sh check</code> 는 빠진 것을
나열합니다. 나열되는 것이 있으면 포크의 전체를 게시하는 <code>build-compose.sh</code> 를 다시
실행하십시오.
Expand All @@ -147,8 +147,8 @@ <h2 id="stale-state">포크를 게시했는데도 의존성 해석이 실패합
</p>
<figure class="codeblock">
<figcaption>출력</figcaption>
<pre><code>ERROR: Unable to resolve dependency org.thisisthepy.compose.foundation:foundation:1.11.1-ext.1
Unable to download checksums of file foundation-1.11.1-ext.1.pom</code></pre>
<pre><code>ERROR: Unable to resolve dependency org.thisisthepy.compose.foundation:foundation:1.11.1-ext.2
Unable to download checksums of file foundation-1.11.1-ext.2.pom</code></pre>
</figure>
<p>
원인은 Kotlin 툴체인의 증분 상태입니다. 포크를 게시하기 전에 돈 빌드가 실패한 해석을
Expand Down
20 changes: 20 additions & 0 deletions renderer/desktop/c/renderer_entry.c
Original file line number Diff line number Diff line change
Expand Up @@ -719,3 +719,23 @@ int32_t dxc_win32_window_zoomed(void *window) {
return 0;
}
#endif

/*
* The names the fork's other desktop wrappers declare, which this image links without ever
* calling. A wrapper's file is reached by the platform switch that names all three loops, and a
* name no C file in the image defines is a link that fails on Linux and Windows.
*/
#ifndef __APPLE__
int32_t dxc_native_metal_allocated_mb(void *device_pointer) {
(void)device_pointer;
return -1;
}
#endif

#ifndef __linux__
void dxc_native_window_begin_drag_at(int32_t edge, float x, float y) {
(void)edge;
(void)x;
(void)y;
}
#endif
24 changes: 12 additions & 12 deletions renderer/desktop/module.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ product: jvm/app
# publishes, and its skiko-awt, which `scripts/publish-skiko-awt.sh` publishes. They carry what
# the toolkit-free windows need and upstream does not have. The fork publishes under its own
# group, org.thisisthepy.compose, so nothing JetBrains publishes can stand in for them, and
# skiko-awt under a version of its own above JetBrains' 0.144.6.
# skiko-awt under org.thisisthepy.compose.skiko, on the same version line.
repositories:
- mavenLocal

Expand All @@ -20,19 +20,19 @@ dependencies:
# native half for each desktop system a build script here supports. The toolchain can pick
# the system only for JetBrains' own desktop module, so every one is named; each loads only
# its own library at run time, and the native image scripts keep only this system's.
- org.thisisthepy.compose.runtime:runtime:1.11.1-ext.1
- org.thisisthepy.compose.desktop:desktop:1.11.1-ext.1
- org.thisisthepy.compose.ui:ui:1.11.1-ext.1
- org.thisisthepy.compose.ui:ui-text:1.11.1-ext.1
- org.thisisthepy.compose.foundation:foundation:1.11.1-ext.1
- org.jetbrains.skiko:skiko-awt:0.144.6.1
- org.thisisthepy.compose.runtime:runtime:1.11.1-ext.2
- org.thisisthepy.compose.desktop:desktop:1.11.1-ext.2
- org.thisisthepy.compose.ui:ui:1.11.1-ext.2
- org.thisisthepy.compose.ui:ui-text:1.11.1-ext.2
- org.thisisthepy.compose.foundation:foundation:1.11.1-ext.2
- org.thisisthepy.compose.skiko:skiko-awt:1.11.1-ext.2
- org.jetbrains.skiko:skiko-awt-runtime-macos-arm64:0.144.6
- org.jetbrains.skiko:skiko-awt-runtime-macos-x64:0.144.6
- org.jetbrains.skiko:skiko-awt-runtime-linux-x64:0.144.6
- org.jetbrains.skiko:skiko-awt-runtime-linux-arm64:0.144.6
- org.jetbrains.skiko:skiko-awt-runtime-windows-x64:0.144.6
# FR-11's example extension draws a Material 3 progress indicator.
- org.thisisthepy.compose.material3:material3:1.11.0-alpha07-ext.1
- org.thisisthepy.compose.material3:material3:1.11.1-ext.2
# Swing's Dispatchers.Main, which a run on a JVM with the toolkit's window needs. The native
# image scripts take it off the image's class path: the windows there answer Dispatchers.Main
# themselves (FrameMainDispatcher).
Expand All @@ -44,12 +44,12 @@ dependencies:
- org.graalvm.sdk:nativeimage:25.0.1: compile-only
# What every window decides the same way, and the AppKit and X11 windows of the native
# image path. The Windows window is still this module's own.
- org.thisisthepy.compose.window:common:0.1.0
- org.thisisthepy.compose.window:graalvm-macos:0.1.0
- org.thisisthepy.compose.window:graalvm-linux:0.1.0
- org.thisisthepy.compose.window:common:1.11.1-ext.2
- org.thisisthepy.compose.window:graalvm-macos:1.11.1-ext.2
- org.thisisthepy.compose.window:graalvm-linux:1.11.1-ext.2

test-dependencies:
- org.thisisthepy.compose.ui:ui-test-junit4:1.11.1-ext.1
- org.thisisthepy.compose.ui:ui-test-junit4:1.11.1-ext.2
- $kotlin.test

settings:
Expand Down
7 changes: 5 additions & 2 deletions renderer/desktop/scripts/build-native-linux.sh
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,10 @@ classpath="$(tr ':' '\n' <<< "$classpath" | grep -v 'kotlinx-coroutines-swing' |
# skiko's native half for every desktop system is on the JVM class path (desktop/module.yaml names
# them all, because the toolchain can pick the system only for JetBrains' own desktop module).
# The image takes this system's alone, as it did when the toolchain picked it.
classpath="$(tr ':' '\n' <<< "$classpath" | grep -v -E 'skiko-awt-runtime-' ;
# JetBrains' skiko-awt comes in as well, because the fork's Compose modules ask for
# org.jetbrains.skiko:skiko, whose JVM half it is. The fork's skiko-awt (a different group) is the
# one the image takes, and two jars of the same classes would leave the choice to class path order.
classpath="$(tr ':' '\n' <<< "$classpath" | grep -v -E 'skiko-awt-runtime-|/org/jetbrains/skiko/skiko-awt/' ;
tr ':' '\n' <<< "$classpath" | grep -E "skiko-awt-runtime-linux-$SKIKO_ARCH-[0-9]" || true)"
classpath="$(paste -sd: - <<< "$classpath")"

Expand All @@ -45,7 +48,7 @@ compose_as="$(sed -n 's/^COMPOSE_AS="\([^"]*\)"$/\1/p' "$compose_script")"
skiko_as="$(sed -n 's/^SKIKO_AWT_AS="\([^"]*\)"$/\1/p' "$compose_script")"
[[ -n "$compose_as" && -n "$skiko_as" ]] || die "$compose_script names no COMPOSE_AS or SKIKO_AWT_AS"
for fork_jar in "repository/org/thisisthepy/compose/ui/ui-desktop/$compose_as/" \
"repository/org/jetbrains/skiko/skiko-awt/$skiko_as/"; do
"repository/org/thisisthepy/compose/skiko/skiko-awt/$skiko_as/"; do
grep -q "$fork_jar" <<< "$(tr ':' '\n' <<< "$classpath")" || die \
"the class path holds no $fork_jar" \
"These are the Compose fork's desktop modules and its skiko-awt, published to the local" \
Expand Down
7 changes: 5 additions & 2 deletions renderer/desktop/scripts/build-native.sh
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,10 @@ classpath="$(tr ':' '\n' <<< "$classpath" | grep -v 'kotlinx-coroutines-swing' |
# skiko's native half for every desktop system is on the JVM class path (desktop/module.yaml names
# them all, because the toolchain can pick the system only for JetBrains' own desktop module).
# The image takes this system's alone, as it did when the toolchain picked it.
classpath="$(tr ':' '\n' <<< "$classpath" | grep -v -E 'skiko-awt-runtime-' ;
# JetBrains' skiko-awt comes in as well, because the fork's Compose modules ask for
# org.jetbrains.skiko:skiko, whose JVM half it is. The fork's skiko-awt (a different group) is the
# one the image takes, and two jars of the same classes would leave the choice to class path order.
classpath="$(tr ':' '\n' <<< "$classpath" | grep -v -E 'skiko-awt-runtime-|/org/jetbrains/skiko/skiko-awt/' ;
tr ':' '\n' <<< "$classpath" | grep -E "skiko-awt-runtime-macos-$SKIKO_ARCH-[0-9]" || true)"
classpath="$(paste -sd: - <<< "$classpath")"

Expand All @@ -47,7 +50,7 @@ compose_as="$(sed -n 's/^COMPOSE_AS="\([^"]*\)"$/\1/p' "$compose_script")"
skiko_as="$(sed -n 's/^SKIKO_AWT_AS="\([^"]*\)"$/\1/p' "$compose_script")"
[[ -n "$compose_as" && -n "$skiko_as" ]] || die "$compose_script names no COMPOSE_AS or SKIKO_AWT_AS"
for fork_jar in "repository/org/thisisthepy/compose/ui/ui-desktop/$compose_as/" \
"repository/org/jetbrains/skiko/skiko-awt/$skiko_as/"; do
"repository/org/thisisthepy/compose/skiko/skiko-awt/$skiko_as/"; do
grep -q "$fork_jar" <<< "$(tr ':' '\n' <<< "$classpath")" || die \
"the class path holds no $fork_jar" \
"These are the Compose fork's desktop modules and its skiko-awt, published to the local" \
Expand Down
Loading
Loading