-
I have a Java (Maven) project that uses okio.BufferedSink: Everything was working fine until I tried to upgrade to okio version 3.4.0 By building okio from source and using the newly built version (in my .m2 repository), I was able to eventually figure out where the cut-off is between working versions and non-working versions is. ...not working after I even found the EXACT commit where it stopped working: I noted something significant when I decompressed the jar files. Inside the last successful commit (1c96e53) I built myself, I can see: The very next commit (40ceab5) I built myself, I see: Here is the github for that commit: I do not know enough about java and kotlin to understand why this change in this commit causes the contents of the .jar file to change so dramatically. By the way, I am using Java 1.8 (Java 8) to build from a terminal on my macOS (m1 processor) laptop. Is the problem somehow related to a change in the way kotlin interop with java on different platforms? What is the error? Well, using version 3.4.0 gives this error: It's almost as if the Java compiler is telling me that it can see the kotlin class in Java, but it is not allowed to use it due to access restriction. Please help! What do I need to do in order to get this working again? I can't use a version prior to 3.4.0 because of a vulnerability identified in versions of okio prior to 3.4.0. Thank you so much for your help! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
I figured it out. This project OkHttpAetherClient uses Takari pom as its parent. This means everything in that parent POM is inherited, including the use of takari-lifecycle for compile. I solved the issue by adding this:
|
Beta Was this translation helpful? Give feedback.
I figured it out. This project OkHttpAetherClient uses Takari pom as its parent. This means everything in that parent POM is inherited, including the use of takari-lifecycle for compile. I solved the issue by adding this: