-
Notifications
You must be signed in to change notification settings - Fork 21
java.lang.AssertionError: assertion failed: ClassBType.info not yet assigned: #11205
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
Comments
It's not easy to guess what the problem could be. I assume you did |
Yes I have run |
Maybe the updated Java sdk is not binary compatible and some of your dependencies need to be re-compiled? Is your project open-source? Or can you create a sample project that reproduces the issue? |
My project isn't open source. I have created a very simple sbt project on github to reproduce it. The sdk source code is under src/main/java. Error message:
|
The sources for that project contain a Java class that extends itself. The build is configured to have If we pass them to // build.sbt
...
compileOrder := CompileOrder.JavaThenScala We see the error:
The error message you encountered is not user friendly, and should certainly be improved. |
There seem to be a couple of errors. No package statement here. Is it only on MacOS that class names are case insensitive? I happen to be on a Mac. If only case classes were case sensitive. We should all be more class sensitive. |
Thanks for pointing this out. I didn't know class name sensitivity with Java could be an issue. Found this on stackoverflow that discussed this in depth. jvm class name sensitivity Strangely the code worked before SDK update. Any way differentiating class name by case sensitivity is bad. Feel free to close the issue. Thanks. |
I am using scala in a production system. Recently a third party payment service provider updated its payment Java sdk, which caused this compilation error.
This is critical for our business. Please help ASAP. Thanks in advance.
We use Scala 2.12.4 and SBT 1.2.1
The text was updated successfully, but these errors were encountered: