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
Make MiMa sbt plugin tell you which artifact/project it is processing #6
Comments
How can it be an error and then reported as 0 problems? |
The first [info] is akka-actor, and the second [info] is akka-testkit. Isn't it obvious? |
I don't think it's obvious that the following is outputted: [error] * class akka.routing.CurrentRoutees was concrete; is declared abstract in new version and then it says: [info] Found 0 potential binary incompatibilities How can something be an error, but not something that needs fixing? |
That's the meaning of this ticket. If the output had looked something like this:
It would make more sense |
Or simply: [error] [akka-actor] [major] * class akka.actor.ReceiveTimeout was concrete; is declared abstract in new version |
Yes, that would be fine as well, but there needs to be an output when it is ok that contains the name as well. |
Output if I in akka do mima-report-binary-issues from the top level (only akka-actor and akka-testkit have been configured)
Kind of hard to see what's ok and what's not.
The text was updated successfully, but these errors were encountered: