Merge branch 'main' into phipag/issue2283

Author: phipag

.github/workflows/check-build.yml

@@ -47,6 +47,7 @@ on:
       - 'powertools-large-messages/**'
       - 'powertools-logging/**'
       - 'powertools-metrics/**'
+      - 'powertools-kafka/**'
       - 'powertools-parameters/**'
       - 'powertools-serialization/**'
       - 'powertools-sqs/**'
@@ -72,6 +73,7 @@ jobs:
           - 11
           - 17
           - 21
+          - 25
     steps:
       - id: checkout
         name: Checkout repository

.github/workflows/security-dependencies-check.yml

@@ -26,6 +26,6 @@ jobs:
       - name: Checkout Repository
         uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
       - name: Verify Contents
-        uses: actions/dependency-review-action@40c09b7dc99638e5ddb0bfd91c1673effc064d8a # v4.8.1
+        uses: actions/dependency-review-action@3c4e3dcb1aa7874d2c16be7d79418e9b7efd6261 # v4.8.2
         with:
           config-file: './.github/dependency-review-config.yml'

README.md

@@ -22,17 +22,17 @@ Powertools for AWS Lambda (Java) is available in Maven Central. You can use your
     <dependency>
         <groupId>software.amazon.lambda</groupId>
         <artifactId>powertools-tracing</artifactId>
-        <version>2.6.0</version>
+        <version>2.7.0</version>
     </dependency>
     <dependency>
         <groupId>software.amazon.lambda</groupId>
-        <artifactId>powertools-logging</artifactId>
-        <version>2.6.0</version>
+        <artifactId>powertools-logging-log4j</artifactId>
+        <version>2.7.0</version>
     </dependency>
     <dependency>
         <groupId>software.amazon.lambda</groupId>
         <artifactId>powertools-metrics</artifactId>
-        <version>2.6.0</version>
+        <version>2.7.0</version>
     </dependency>
     ...
 </dependencies>
@@ -116,6 +116,7 @@ Next, configure the aspectj-maven-plugin to compile-time weave (CTW) the aws-lam
             aspect 'software.amazon.lambda:powertools-logging:{{ powertools.version }}'
             aspect 'software.amazon.lambda:powertools-tracing:{{ powertools.version }}'
             aspect 'software.amazon.lambda:powertools-metrics:{{ powertools.version }}'
+            implementation 'software.amazon.lambda:powertools-logging-log4j:{{ powertools.version }}'
             implementation "org.aspectj:aspectjrt:1.9.22"
         }
         
@@ -126,10 +127,10 @@ Next, configure the aspectj-maven-plugin to compile-time weave (CTW) the aws-lam
 
 
 ### Java Compatibility
-Powertools for AWS Lambda (Java) supports all Java version from 11 up to 21 as well as the
-[corresponding Lambda runtimes](https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html).
+Powertools for AWS Lambda (Java) supports all Java versions from 11 to 25 in line with the [corresponding Lambda runtimes](https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html).
+
 For the modules that provide annotations, Powertools for AWS Lambda (Java) leverages the **aspectj** library.
-You may need to add the good version of `aspectjrt` to your dependencies based on the JDK used for building your function:
+You may need to add the appropriate version of `aspectjrt` to your dependencies based on the JDK used for building your function:
 
 ```xml
 <dependency>
@@ -142,12 +143,13 @@ You may need to add the good version of `aspectjrt` to your dependencies based o
 <details>
     <summary><b>JDK - aspectj dependency matrix</b></summary>
 
+Use the following [dependency matrix](https://github.com/eclipse-aspectj/aspectj/blob/master/docs/release/JavaVersionCompatibility.adoc) to understand which AspectJ version to use based on your JDK version:
+
 | JDK version | aspectj version        |
 |-------------|------------------------|
 | `11-17`     | `1.9.20.1` (or higher) |
 | `21`        | `1.9.21` (or higher)   |
-
-More info [here](https://github.com/aws-powertools/powertools-lambda-java/pull/1519/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R191).
+| `25`        | `1.9.25` (or higher)   |
 
 </details>
 

docs/Dockerfile

@@ -1,4 +1,4 @@
-FROM squidfunk/mkdocs-material@sha256:58dee36ad85b0ae4836522ee6d3f0150d828bca9a1f7d3bfbf430bca771c1441
+FROM squidfunk/mkdocs-material@sha256:980e11fed03b8e7851e579be9f34b1210f516c9f0b4da1a1457f21a460bd6628
 
 COPY requirements.txt /tmp/
 RUN pip install --require-hashes -r /tmp/requirements.txt

docs/FAQs.md

@@ -7,6 +7,8 @@ description: Frequently Asked Questions
 
 Many utilities in this library use `aspectj-maven-plugin` to compile-time weave (CTW) aspects into the project. In case you want to use `Lombok` or other compile-time preprocessor for your project, it is required to change `aspectj-maven-plugin` configuration to enable in-place weaving feature. Otherwise the plugin will ignore changes introduced by `Lombok` and will use `.java` files as a source.
 
+Alternatively, you can use the [functional approach](./usage-patterns.md#functional-approach) which does not require AspectJ configuration.
+
 To enable in-place weaving feature you need to use following `aspectj-maven-plugin` configuration:
 
 ```xml hl_lines="2-6"
@@ -31,6 +33,8 @@ To enable in-place weaving feature you need to use following `aspectj-maven-plug
 Many utilities use `aspectj-maven-plugin` to compile-time weave (CTW) aspects into the project. When using it with Kotlin projects, it is required to `forceAjcCompile`.
 No explicit configuration should be required for gradle projects.
 
+Alternatively, you can use the [functional approach](./usage-patterns.md#functional-approach) which does not require AspectJ configuration.
+
 To enable `forceAjcCompile` you need to use following `aspectj-maven-plugin` configuration:
 
 ```xml hl_lines="2"