-
Notifications
You must be signed in to change notification settings - Fork 107
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
Not clear why build is breaking #151
Comments
Are you using the latest version? Newer versions of japicmp print out the exact reason for a source or binary incompatible change in the XML (for example):
Can you provide the XML file for the latest version? Thanks in advance. |
@siom79 Yes, please reopen this issue. I am using version 0.9.1. Unfortunately Github won't allow me to attach XML files (even ZIP doesn't work for some reason). Please download the file from https://bitbucket.org/cowwoc/requirements/downloads/japicmp.xml and attach it to this issue on my behalf. The "cause" message I get starts with this text It goes on to list many more entries, but as I mentioned above all of them seem to be related to the addition of new interfaces that didn't exist before. #112 was supposed to fix this problem. Perhaps we are looking at a regression? |
Thanks for providing the details. It helped me to reconstruct your case. I could fix it on the |
Sounds good. I'll keep my eyes open for that release. Thanks! |
@siom79 I tested the |
Released with 0.9.2. |
If you look at the attached report, it's not clear why japicmp is failing the build. As far as I can tell, the report contains the following changes:
Neither of these should break source or binary compatibility.
japicmp.pdf
The text was updated successfully, but these errors were encountered: