Closed mateuszkwiecinski closed 11 months ago
Those classes are compileOnly
, so I'm not sure why proguard is complaining. Can you try adding the dontwarn
rule to your build to see if it passes?
I'm far from understanding R8 internals, but I believe the compileOnly
dependency is exactly the reason why R8 cannot access and read the class, so it is unable to check how mordant classes interact with them to establish if they can be removed from final jar π
I added -dontwarn
s and it passed the build :)
I'm using mordant via
clikt
and its latest release4.2.1
pulls the most recent mordant version which according to what I saw started providing their own Proguard/R8 rules (π). Unfortunately the rules were not updated to match latest code changes, and the build now fails withSo I guess grallvm-related references should be kept somehow too? I'm not sure how they are used, so maybe ignoring them is the proper choice (
-dontwarn org.graalvm.**
)?If needed, failing build can be found here: https://github.com/usefulness/diffuse/actions/runs/6421384714/job/17435616654?pr=238 build scan: https://scans.gradle.com/s/fkzlsu76u35ce/console-log?anchor=162&page=1