-
Notifications
You must be signed in to change notification settings - Fork 53
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
passing comma separated list of jars broken #27
Comments
Hello, Comma-separated arguments are not supported anymore (too difficult to support). Sorry for inconvenience. Multiple jars should be passed to the tool via XML descriptor: http://lvc.github.io/japi-compliance-checker/#Adv_Usage Supported arguments:
If you'd like to analyze multiple jars then you'd better to look at the https://github.com/lvc/japi-tracker and https://github.com/lvc/japi-monitor tools based on the japi-compliance-checker. Thank you. |
okay, we'll get our tooling updated for the change. any chance you could update the japi-compliance-checker version to 2.0 to flag the breaking change in behavior? |
I'll bump version to 2.0 after adding more libraries to the upstream tracker and fixing related bugs: http://abi-laboratory.pro/java/tracker/ This will make the 2.0 version more stable. Thank you. |
sounds good! |
looks like the change in commit e206a1d broke the ability to pass a comma separated list of jars instead of a descriptor file.
with that change in place, when I give a list of jars I get this error:
If I go back to prior to that commit then the list of jars is properly handled.
the invocation is in this hbase script for building the list of jars
The text was updated successfully, but these errors were encountered: