Skip to content

Commit

Permalink
[docs] Restore changelog
Browse files Browse the repository at this point in the history
  • Loading branch information
valfirst committed Dec 19, 2022
1 parent 0f71267 commit f9911ef
Showing 1 changed file with 160 additions and 0 deletions.
160 changes: 160 additions & 0 deletions src/site/markdown/changelog.md
Expand Up @@ -5,6 +5,166 @@
Introduce a new `capture.level` property and API to control captured events globally,
see https://github.com/valfirst/slf4j-test/issues/314.

### [slf4j-test-2.6.1](https://github.com/valfirst/slf4j-test/tree/slf4j-test-2.6.1) (2022-04-01)
[Full Changelog](https://github.com/valfirst/slf4j-test/compare/slf4j-test-2.6.0...slf4j-test-2.6.1)

**Fixes:**
- [#255](https://github.com/valfirst/slf4j-test/issues/255) via [#257](https://github.com/valfirst/slf4j-test/pull/257) Fix memory leak when clearing logs in all threads (by [@sofiamorseletto](https://github.com/sofiamorseletto))
Going back to the custom `ThreadLocal` implementation (`uk.org.lidalia.lang.ThreadLocal`) in order to prevent memory leaks.

### [slf4j-test-2.6.0](https://github.com/valfirst/slf4j-test/tree/slf4j-test-2.6.0) (2022-03-21)
[Full Changelog](https://github.com/valfirst/slf4j-test/compare/slf4j-test-2.5.0...slf4j-test-2.6.0)

**Implemented enhancements:**
- [#247](https://github.com/valfirst/slf4j-test/pull/247) Log events found when AssertJ assertion fails (by [@jamietanna](https://github.com/jamietanna))

This helps quite a bit with diagnosing why an assertion fails, as the alternative is to either attach a debugger or `System.out.println` the logging events found.
- [#250](https://github.com/valfirst/slf4j-test/issues/250) via [#251](https://github.com/valfirst/slf4j-test/pull/251) Add TCCL attribute to `LoggingEvent` (by [@sofiamorseletto](https://github.com/sofiamorseletto))

The changes add an attribute on `LoggingEvent` which contains the Thread Context Classloader used when the logging event was created. This allows the assertion of the TCCL of a certain log to check that the log was handled by the correct classloader.

**Updates:**
- Bump `org.slf4j:slf4j-api` from `2.0.0-alpha6` to `2.0.0-alpha7`
- Bump `com.google.guava:guava` from `31.0.1-jre` to `31.1-jre`
- Bump `joda-time:joda-time` from `2.10.13` to `2.10.14`

### [slf4j-test-2.5.0](https://github.com/valfirst/slf4j-test/tree/slf4j-test-2.5.0) (2022-02-08)
[Full Changelog](https://github.com/valfirst/slf4j-test/compare/slf4j-test-2.4.1...slf4j-test-2.5.0)

**Updates:**
- [#228](https://github.com/valfirst/slf4j-test/pull/228) - Bump `org.slf4j:slf4j-api` from `2.0.0-alpha5` to `2.0.0-alpha6`

_NOTE:_ `slf4j-test:2.5.0` is compatible with `slf4j-api:2.0.0-alpha6`and higher and it is not compatible with previous versions (see [compatibility matrix](https://github.com/valfirst/slf4j-test/blob/master/README.md#compatibility-matrix) for more details). The root cause is breaking changes in SLF4J API:
- [breaking change 1](https://github.com/qos-ch/slf4j/commit/62a265d3c5a2bde82f2e025ee10f115564d951bb#diff-d9b428b7088f0b9ee7b67586509f3920e88f408e06258a0e2113c8cb8f4c8e37)
- [breaking change 2](https://github.com/qos-ch/slf4j/commit/f09e33dd15f60b4480d9a60bfb9083ef739fea2f#diff-d9b428b7088f0b9ee7b67586509f3920e88f408e06258a0e2113c8cb8f4c8e37)
- Bump `org.assertj:assertj-core` from `3.21.0` to `3.22.0`

### [slf4j-test-2.4.1](https://github.com/valfirst/slf4j-test/tree/slf4j-test-2.4.1) (2021-12-23)
[Full Changelog](https://github.com/valfirst/slf4j-test/compare/slf4j-test-2.4.0...slf4j-test-2.4.1)

**Implemented enhancements:**
- [#207](https://github.com/valfirst/slf4j-test/pull/207) - Enable assertions to be made on LoggingEvents from any thread (by [@topbadger](https://github.com/topbadger))

The current implementation only verifies against the `LoggingEvent`s captured by the thread that is running the test. `TestLogger` provides access to all events captured across any thread via `TestLogger::getAllLoggingEvents()` so a modifying method has been added to the assertion class to allow the assertion mode to be switched.

Example usage:
```
assertThat(logger).anyThread().hasLogged(...);
```
- [#220](https://github.com/valfirst/slf4j-test/issues/220) via [#221](https://github.com/valfirst/slf4j-test/pull/221) - Format `null`-s in `LoggingEvent#getFormattedMessage()` the same way as `SLF4J` (by [@josephw](https://github.com/josephw))

`LoggingEvent#getFormattedMessage()` is public ([#23](https://github.com/valfirst/slf4j-test/issues/23)). However, it hasn't presented `null` values the same way as SLF4J, due to un-matched wrapping/unwrapping of `Optional`:
```
LoggingEvent e = new LoggingEvent(Level.INFO, "Content: {}, {}", null, "value");
System.out.println(e.getFormattedMessage());
```

Produced previously:
```
Content: Optional.empty, value
```
Produces now:
```
Content: null, value
```

**Updates:**
- Bump `org.slf4j:slf4j-api` from `2.0.0-alpha4` to `2.0.0-alpha5`
- Bump `joda-time:joda-time` from `2.10.10` to `2.10.13`
- Bump `com.google.guava:guava` from `30.1.1-jre` to `31.0.1-jre`
- Bump `org.assertj:assertj-core` from `3.20.2` to `3.21.0`

### [slf4j-test-2.4.0](https://github.com/valfirst/slf4j-test/tree/slf4j-test-2.4.0) (2021-08-25)
[Full Changelog](https://github.com/valfirst/slf4j-test/compare/slf4j-test-2.3.0...slf4j-test-2.4.0)

**Updates:**

- [#190](https://github.com/valfirst/slf4j-test/pull/190) - Bump `org.slf4j:slf4j-api` from `2.0.0-alpha2` to `2.0.0-alpha4`
- [#190](https://github.com/valfirst/slf4j-test/pull/190) - Update according to the changes in SLF4J API `2.0.0-alpha3`

_NOTE:_ `slf4j-test:2.4.0` is compatible with `slf4j-api:2.0.0-alpha3`and higher and it is not compatible with previous versions (see [compatibility matrix](https://github.com/valfirst/slf4j-test/blob/master/README.md#compatiblity-matrix) for more details). The root cause is [breaking change in SLF4J API](https://github.com/qos-ch/slf4j/commit/3e2381ea694c23c897433d675facd9a799a52256#diff-2f5a94db3233a499f03f72a41ebd7fed35029b270f9a7578c202db4ab1845b48).

### [slf4j-test-2.3.0](https://github.com/valfirst/slf4j-test/tree/slf4j-test-2.3.0) (2021-08-05)
[Full Changelog](https://github.com/valfirst/slf4j-test/compare/slf4j-test-2.2.0...slf4j-test-2.3.0)

**Implemented enhancements:**

- [#184](https://github.com/valfirst/slf4j-test/pull/184) - Add assertion for substrings of log messages (by [@jamietanna](https://github.com/jamietanna))
- [#187](https://github.com/valfirst/slf4j-test/pull/187) - Add assertions based on `LoggingEvent` (by [@jamietanna](https://github.com/jamietanna))

**Internals:**
- [#185](https://github.com/valfirst/slf4j-test/issues/185) via [#186](https://github.com/valfirst/slf4j-test/pull/186) Enforce consistent code style (by [@jamietanna](https://github.com/jamietanna))

### [slf4j-test-2.2.0](https://github.com/valfirst/slf4j-test/tree/slf4j-test-2.2.0) (2021-07-29)
[Full Changelog](https://github.com/valfirst/slf4j-test/compare/slf4j-test-2.1.1...slf4j-test-2.2.0)

**Implemented enhancements:**

- [#181](https://github.com/valfirst/slf4j-test/issues/181) via [#182](https://github.com/valfirst/slf4j-test/pull/182) - Add initial AssertJ assertions (by [@jamietanna](https://github.com/jamietanna))

**Updates:**

- [#124](https://github.com/valfirst/slf4j-test/issues/124) via [#126](https://github.com/valfirst/slf4j-test/pull/126) - Add [an explicit license](https://github.com/valfirst/slf4j-test/blob/master/LICENSE) to the project
- Bump `org.slf4j:slf4j-api` from 1.8.0-beta2 to 2.0.0-alpha2
- Bump `joda-time:joda-time` from 2.10 to 2.10.10
- Bump `com.google.guava:guava` from 26.0-jre to 30.1.1-jre

### [slf4j-test-2.1.1](https://github.com/valfirst/slf4j-test/tree/slf4j-test-2.1.1) (2018-09-17)
[Full Changelog](https://github.com/valfirst/slf4j-test/compare/slf4j-test-2.1.0...slf4j-test-2.1.1)

**Implemented enhancements:**

- Make LoggingEvent self-descriptive: implement `toString` method (by [@valfirst](https://github.com/valfirst))

**Updates:**

- Bump `com.google.guava:guava` from 25.1-jre to 26.0-jre

### [slf4j-test-2.1.0](https://github.com/valfirst/slf4j-test/tree/slf4j-test-2.1.0) (2018-06-29)
[Full Changelog](https://github.com/valfirst/slf4j-test/compare/slf4j-test-2.0.0...slf4j-test-2.1.0)

**Implemented enhancements:**

- [#23](https://github.com/valfirst/slf4j-test/issues/23) - Make LoggingEvent\#getFormattedMessage public (by [@valfirst](https://github.com/valfirst))
- Drop `uk.org.lidalia:lidalia-lang` dependency (by [@valfirst](https://github.com/valfirst))

**Updates:**

- Bump `org.slf4j:slf4j-api` from 1.8.0-beta1 to 1.8.0-beta2
- Bump` joda-time:joda-time` from 2.9.9 to 2.10
- Bump `com.google.guava:guava` from 24.1-jre to 25.1-jre

### [slf4j-test-2.0.0](https://github.com/valfirst/slf4j-test/tree/slf4j-test-2.0.0) (2018-03-19)
[Full Changelog](https://github.com/valfirst/slf4j-test/compare/slf4j-test-1.3.0...slf4j-test-2.0.0)

**Breaking changes**

- Increase minimum required JDK version from 7 to 8
- Change base package to `com.github.valfirst` to reflect ownership

**Implemented enhancements:**

- [#6](https://github.com/valfirst/slf4j-test/pull/6) - Implement JUnit 5 support (by [@valfirst](https://github.com/valfirst))
- Optimize performance: replace CopyOnWriteArrayList with Collections.synchronizedList in `TestLoggerFactory` (by [@valfirst](https://github.com/valfirst))

**Updates:**

- Bump `org.slf4j:slf4j-api` from 1.8.0-beta0 to 1.8.0-beta2
- Bump `com.google.guava:guava` from 20.0 to 24.1-jre

### [slf4j-test-1.3.0](https://github.com/valfirst/slf4j-test/tree/slf4j-test-1.3.0) (2018-01-05)
[Full Changelog](https://github.com/valfirst/slf4j-test/compare/slf4j-test-1.2.0...slf4j-test-1.3.0)

**`groupId` was changed to `com.github.valfirst` to reflect ownership**

**Implemented enhancements:**

- Support new SLF4J binding mechanism introduced in [SLF4J 1.8](https://www.slf4j.org/faq.html#changesInVersion18)

**Updates:**

- Upgrade to Guava 20.0, Joda Time 2.9.9

### Version 1.2.0

Allows construction of standalone instances to facilitate logging in different
Expand Down

0 comments on commit f9911ef

Please sign in to comment.