-
Notifications
You must be signed in to change notification settings - Fork 71
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
MiMa does not like jars with a module-info.class #206
Milestone
Comments
schmitch
changed the title
MiMa does not like jaxb-api.jar/Multi-Release JAR
MiMa does not like jars with a module-info.jar
Apr 26, 2018
schmitch
changed the title
MiMa does not like jars with a module-info.jar
MiMa does not like jars with a module-info.class
Apr 26, 2018
Yup. Ignoring |
What is more, MiMa does not usually check BC of the dependencies. Therefore it should not fail if a dependency has something that it can not parse. |
is there a timeframe for 0.2.1? |
I'm at Scala Days Berlin, so I'll try and get it out next week. |
jeffmay
added a commit
to rallyhealth/play-module-json-error-handler
that referenced
this issue
Sep 28, 2018
- Upgrade to sbt 1.0 to solve a weird bug with MiMa (lightbend-labs/mima#206) - Add missing resolver - Remove name supression config - Fix resolver issue
jeffmay
added a commit
to rallyhealth/play-module-json-error-handler
that referenced
this issue
Sep 28, 2018
- Upgrade to sbt 1.0 to solve a weird bug with MiMa (lightbend-labs/mima#206) - Add missing resolver - Remove name supression config - Fix resolver issue
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently when adding jaxb-api.jar to a project with MiMa enabled, MiMa can't analyze Binary Incompatible changes.
When adding it to Play I get the following error:
java.lang.RuntimeException: bad constant pool tag 19 at byte 54
The problem is that this jar contains a
module-info.class
which basically just gets ignored by java8/scala/sbt. However MiMa still tries to analyze it and will fail with the Exception.The text was updated successfully, but these errors were encountered: