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
XmlUnit 2.6.[3,4] is not compatible with AssertJ-Core 3.15.0 #181
Comments
I'm not an AssertJ user myself. I wonder whether the AssertJ devs realize they are breaking binary compatibility repeatedly and make people who provide custom assertions unhappy. This is not the first time, see #135 and #166 I'll try to see whether there is a way to adapt without breaking support for older versions - unless @krystiankaluzny beats me to it. |
I've simply overridden the method and duplicated the implementation -which hasn't changed since at least 2.9.0. Calling I've also added an easier setup for compatibility tests in Travis. |
I've just published a 2.7.0-SNAPSHOT version. @jwalter it would be good if yo could confirm this version works for you. |
2.7.0-SNAPSHOT solves the reported issue for me. Thanks! |
will do tonight (CEST :-) ) Thanks for testing. |
2.7.0 should show up in maven central soonish, I've just released the Nexus repo. |
The following test:
will throw an error when trying to run with assertj 3.15.0 on the classpath:
The cause is that assertj 3.15.0 moved the `describedAs´method from AbstractAssert to Descriptable and due to type erasure the method return type changed on the byte code level from AbstractAssert to Object.
This currently affects all Spring Boot projects using the milestone M2, M3 or M4 builds of Spring Boot 2.3.0.
The text was updated successfully, but these errors were encountered: