NIFI-14998 - Bump Log4J2 to 2.25.2, Guava to 33.5.0-jre, Mockito to 5.20.0, and others

[pvillard31]

Summary

NIFI-14998 - Bump Log4J2 to 2.25.2, Guava to 33.5.0-jre, Mockito to 5.20.0, and others

• Jetbrains Annotations from 24.1.0 to 26.0.2-1 - https://github.com/JetBrains/java-annotations/releases/tag/26.0.2-1
• Eclipse JDT ECJ from 3.42.0 to 3.43.0 - https://github.com/eclipse-jdt/eclipse.jdt.core
• Guava from 33.4.8-jre to 33.5.0-jre - https://github.com/google/guava/releases/tag/v33.5.0
• Jakarta Mail API from 2.1.4 to 2.1.5 - https://github.com/jakartaee/mail-api/releases/tag/2.1.5
• PostgreSQL from 42.7.7 to 42.7.8 - https://github.com/pgjdbc/pgjdbc/releases/tag/REL42.7.8
• Error Prone Annotations from 2.33.0 to 2.42.0 - https://github.com/google/error-prone/releases/tag/v2.42.0
• AWS SDK v2 from 2.33.12 to 2.34.0 - https://github.com/aws/aws-sdk-java-v2/blob/master/CHANGELOG.md
• Log4J2 from 2.25.1 to 2.25.2 - https://github.com/apache/logging-log4j2/releases/tag/rel%2F2.25.2
• Mockito from 5.19.0 to 5.20.0 - https://github.com/mockito/mockito/releases/tag/v5.20.0

Tracking

Please complete the following tracking steps prior to pull request creation.

Issue Tracking

• Apache NiFi Jira issue created

Pull Request Tracking

• Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
• Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

• Pull Request based on current revision of the main branch
• Pull Request refers to a feature branch with one commit containing changes

Verification

Please indicate the verification steps performed prior to pull request creation.

Build

• Build completed using ./mvnw clean install -P contrib-check
  • JDK 21
  • JDK 25

Licensing

• New dependencies are compatible with the Apache License 2.0 according to the License Policy
• New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

• Documentation formatting appears as expected in rendered files

[exceptionfactory]

Thanks for working on these upgrades @pvillard31.

Regarding the Guava version, this has not previously been set at the root level due to incompatible changes in various modules. This seems to be less of an issue with recent versions of Guava. However, Guava should be avoided in general, so leaving the version in particular modules help keep the dependency isolated. For these reasons, I recommend reverting the root-level version change and keeping the Guava version property in the previous locations.

[pvillard31]

Done, thanks for the feedback @exceptionfactory