We've got an OSGI project that uses both assertj and xmlunit-assertj ( https://github.com/xmlunit/xmlunit )
But now we get issues with that xmlunit uses the Failures class while this is not exposed.
The reason why they use it is to:
- determine whether or not to filter (their own) elements from the exception's stacktrace. (not avoidable)
- create the AssertionError class. (avoidable)
I've been looking at the xmlunit-assertj code and checking if I could find another way to achieve this without usage of the Failures class but did not find it.
I could avoid the creation of the AssertionError route, but I would still end up with the same problem concerning the first point.
We've got an OSGI project that uses both assertj and xmlunit-assertj ( https://github.com/xmlunit/xmlunit )
But now we get issues with that xmlunit uses the Failures class while this is not exposed.
The reason why they use it is to:
I've been looking at the xmlunit-assertj code and checking if I could find another way to achieve this without usage of the Failures class but did not find it.
I could avoid the creation of the AssertionError route, but I would still end up with the same problem concerning the first point.