-
Notifications
You must be signed in to change notification settings - Fork 407
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.14.0 compatibility errors #509
Comments
This will take some investigation. I haven't checked anything, but I can only wonder the following:
|
It appears the strangeness with MiMa is new functionality about
|
@ashawley Jeez, this is all pretty intense. It's too bad the 2.13 release used a different commit. My suggestion is probably for us to exclude the new functionality for now, fix anything else that is definitely broken, and the reenable it and see where we stand. |
(Also apologies for my silence -- I'm in the middle of moving to a new apartment so outside of work I've been quite busy recently.) |
Changing |
I agree. I've opened lightbend-labs/mima#375 |
The summary of lightbend-labs/mima#375 is that making object methods package-private is not binary compatible for Java callers of the static forwarders. Java callers are probably not a case ScalaCheck needs to worry about, especially for |
MiMa was going to be updated in #508 to version 0.5.0 from 0.3.0, but there are a lot of complaints. They also aren't the same complaints: They differ for Scala version, and for compiler target (JVM v. JS).
The 1.14.0 release was made from 9b4d431
The 1.14.0 release for 2.13.0 was made from 492ab2d
Here are the MiMa failures that have been collated and modified for brevity:
JVM
JS
The text was updated successfully, but these errors were encountered: