diff --git a/README.md b/README.md index 34882d5..1e9ef1e 100644 --- a/README.md +++ b/README.md @@ -49,6 +49,7 @@ logCapture.assertLoggedInOrder( * [Cucumber example](#cucumber-example) * [Cucumber feature file](#cucumber-feature-file) * [Changes](#changes) + * [3.6.2](#362) * [3.6.1](#361) * [3.6.0](#360) * [3.5.0](#350) @@ -73,7 +74,7 @@ Add log-capture as a test dependency to your project. If you use Maven, add this de.dm.infrastructure log-capture - 3.6.1 + 3.6.2 test ``` @@ -309,6 +310,10 @@ And with MDC logging context ## Changes +### 3.6.2 + +* Fixed an assertion message concerning captured Exceptions. + ### 3.6.1 * Fixed a misleading and wrong assertion message. The assertion itself was correct, but the message always said all matchers did not match when only a subset did not match. diff --git a/pom.xml b/pom.xml index e42f49a..f622c09 100644 --- a/pom.xml +++ b/pom.xml @@ -1,5 +1,5 @@ - 4.0.0 @@ -29,7 +29,7 @@ - 3.5.0-SNAPSHOT + 3.6.2-SNAPSHOT 1.8 1.18.22 diff --git a/src/main/java/de/dm/infrastructure/logcapture/ExpectedException.java b/src/main/java/de/dm/infrastructure/logcapture/ExpectedException.java index 03f1f69..9da6e6b 100644 --- a/src/main/java/de/dm/infrastructure/logcapture/ExpectedException.java +++ b/src/main/java/de/dm/infrastructure/logcapture/ExpectedException.java @@ -62,7 +62,7 @@ private static String loggedExceptionToString(Optional