aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorReinier Zwitserloot <r.zwitserloot@projectlombok.org>2021-12-21 02:03:39 +0100
committerReinier Zwitserloot <r.zwitserloot@projectlombok.org>2021-12-21 02:03:39 +0100
commitbe551db9eed2ff7786f82e5d3d455f9f220b2072 (patch)
treed54774d699aa104d4f7e58ae992ce19f1611333e /doc
parent6d2a474e55db3937eafa5a6d089efd5ba75a62bf (diff)
downloadlombok-be551db9eed2ff7786f82e5d3d455f9f220b2072.tar.gz
lombok-be551db9eed2ff7786f82e5d3d455f9f220b2072.tar.bz2
lombok-be551db9eed2ff7786f82e5d3d455f9f220b2072.zip
[Issue #2849] Mention the implementation of this feature in the changelog
Diffstat (limited to 'doc')
-rw-r--r--doc/changelog.markdown4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/changelog.markdown b/doc/changelog.markdown
index a1938014..b6b42b39 100644
--- a/doc/changelog.markdown
+++ b/doc/changelog.markdown
@@ -2,9 +2,11 @@ Lombok Changelog
----------------
### v1.18.24 "Edgy Guinea Pig"
+
+* FEATURE: `@ToString` has an annotation parameter called `onlyExplicitlyIncluded`. There's now a config key `lombok.toString.onlyExplicitlyIncluded` to set this property as well. [Issue #2849](https://github.com/projectlombok/lombok/pull/2849).
* FEATURE: Turning a field named `uShape` into a getter is tricky: `getUShape` or `getuShape`? The community is split on which style to use. Lombok does `getUShape`, but if you prefer the `getuShape` style, add to `lombok.config`: `lombok.accessors.capitalization = beanspec`. [Issue #2693](https://github.com/projectlombok/lombok/issues/2693) [Pull Request #2996](https://github.com/projectlombok/lombok/pull/2996). Thanks __@YonathanSherwin__!
* BUGFIX: Various save actions and refactor scripts in eclipse work better. [Issue #2995](https://github.com/projectlombok/lombok/issues/2995) [Issue #1309](https://github.com/projectlombok/lombok/issues/1309) [Issue #2985](https://github.com/projectlombok/lombok/issues/2985) [Issue #2509](https://github.com/projectlombok/lombok/issues/2509)
-* NOTE: A widely reported security issue with log4j2 ([CVE-2021-44228](https://www.randori.com/blog/cve-2021-44228/)) has absolutely no effect on either lombok itself nor does usage of lombok on its own, or even the usage of lombok's `@Log4j2`, cause any issues whatsoever: You have to ship your own log4j2 dependency in your app - update that to 2.15 or otherwise mitigate this issue (see the CVE page). To avoid unneccessary warnings from dependency checkers, our dep on log4j2, which is used solely for testing and cannot be exploited in any way, has been updated to 2.15.0. [Issue #3063](https://github.com/projectlombok/lombok/issues/3063)
+* SECURITY: A widely reported security issue with log4j2 ([CVE-2021-44228](https://www.randori.com/blog/cve-2021-44228/)) has absolutely no effect on either lombok itself nor does usage of lombok on its own, or even the usage of lombok's `@Log4j2`, cause any issues whatsoever: You have to ship your own log4j2 dependency in your app - update that to 2.17 or otherwise mitigate this issue (see the CVE page). To avoid unneccessary warnings from dependency checkers, our dep on log4j2, which is used solely for testing, isn't shipped by us, and cannot be exploited in any way, has been updated to 2.17.0. [Issue #3063](https://github.com/projectlombok/lombok/issues/3063)
### v1.18.22 (October 6th, 2021)
* PLATFORM: JDK17 support added. [Issue #2898](https://github.com/projectlombok/lombok/issues/2898).