mirror of
https://github.com/fromchat-messenger/app.git
synced 2026-11-16 02:44:54 +03:00
b0159eb987
Compose Desktop's AbstractProguardTask builds ProGuard's -libraryjars by walking <javaHome>/jmods and nothing else. Adoptium stopped shipping the jmods/ directory in JDK 25 archives (verified: 0 jmods entries in both the linux/x64 and macOS/aarch64 Temurin 25.0.4.1 tarballs, vs 71 for Temurin 17), so on the runners the desktop packaging JDK resolves to /usr/lib/jvm/temurin-25-jdk-amd64 and ProGuard gets no JDK whatsoever. Every class then fails to resolve java.lang.Object — 1.3M "can't find superclass or interface java.lang.Object" warnings, followed by "Please correct the above warnings first". This is why the Java 25 toolchain bump broke every release while the v1.2.0-beta release on the toolchain 17 build kept working, and why a local build with the JetBrains Runtime (which does ship jmods) succeeded while CI did not. ProGuard's version was never the cause; 7.10.0 was still kept because it is what understands this project's Kotlin 2.4 metadata. Install Zulu 25 (still ships jmods) in the desktop-proguard job and export it as FROMCHAT_PACKAGING_JDK; setup-java runs before Temurin 17 so JAVA_HOME stays on 17 for Gradle and the Android build. resolvePackagingJdkHome() now warns loudly when the JDK it picks has no jmods/, instead of leaving it to ProGuard's wall of warnings.
b0159eb987
·
2026-10-16 18:45:41 +03:00
History