Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NIFI-14021 - Upgrade Spring to 6.2.0 and other dependencies #9531

Closed
wants to merge 4 commits into from

Conversation

pvillard31
Copy link
Contributor

@pvillard31 pvillard31 commented Nov 18, 2024

Summary

NIFI-14021 - Upgrade Spring to 6.2.0 and other dependencies

Tracking

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

Issue Tracking

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 mvn clean install -P contrib-check
    • JDK 21

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

- Azure BOM from 1.2.28 to 1.2.29
- MSAL4J from 1.17.1 to 1.17.2
- GCP BOM from 26.49.0 to 26.50.0
- AWS SDK v1 from 1.12.777 to 1.12.778
- AWS SDK v2 from 2.29.1 to 2.29.15
- Groovy from 4.0.23 to 4.0.24
- Spring Framework from 6.1.14 to 6.2.0
- Swagger annotation from 2.2.25 to 2.2.26

Signed-off-by: Pierre Villard <[email protected]>
@pvillard31
Copy link
Contributor Author

Looking into test failures.

@exceptionfactory
Copy link
Contributor

Thanks for working on these upgrades @pvillard31. Following up from a separate conversation, I pushed a commit setting explicit port values for the proxy request resolution test method. This aligns with current behavior and addresses the test failure due to stricter URI parsing in Spring Framework 6.2.

@pvillard31
Copy link
Contributor Author

Thanks @exceptionfactory for tracking down all the of the required changes to fix test failures!

Copy link
Contributor

@exceptionfactory exceptionfactory left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With all tests passing, local verification also looks good. +1 merging

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants