You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After updating to assertj-core 3.11.1 I've started seeing:
java.lang.NoSuchMethodError: org.assertj.core.api.Assertions.assertThat(Ljava/lang/String;)Lorg/assertj/core/api/AbstractCharSequenceAssert;
at com.revinate.assertj.json.JsonPathAssert.jsonPathAsString(JsonPathAssert.java:32)
when running my tests.
This seems to have been caused by a signature changes in the fix for assertj/assertj#1269, in particular the change to Assertions.java:
- public static AbstractCharSequenceAssert<?, String> assertThat(String actual) {+ public static AbstractStringAssert<?> assertThat(String actual) {
I think it's sufficient to just bump the assertj-core dependency to 3.11.1 to fix this, though probably jsonPathAsString should return an AbstractStringAssert<?> rather than AbstractCharSequenceAssert<?, String> to pick up the additional methods that were added in that assertj-core change.
The text was updated successfully, but these errors were encountered:
ljrmorgan
added a commit
to ljrmorgan/assertj-json
that referenced
this issue
Jan 14, 2019
After updating to assertj-core 3.11.1 I've started seeing:
when running my tests.
This seems to have been caused by a signature changes in the fix for assertj/assertj#1269, in particular the change to Assertions.java:
I think it's sufficient to just bump the assertj-core dependency to 3.11.1 to fix this, though probably
jsonPathAsString
should return anAbstractStringAssert<?>
rather thanAbstractCharSequenceAssert<?, String>
to pick up the additional methods that were added in that assertj-core change.The text was updated successfully, but these errors were encountered: