[Snyk] Security upgrade org.springframework.boot:spring-boot-starter-jetty from 2.2.5.RELEASE to 3.2.0

[benjaminhuo]

Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

• builders/testdata/java/springboot-helloworld/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Incorrect Implementation of Authentication Algorithm SNYK-JAVA-ORGECLIPSEJETTY-18230938	721	org.springframework.boot:spring-boot-starter-jetty: 2.2.5.RELEASE -> 3.2.0 Major version upgrade No Known Exploit

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[benjaminhuo]

This is a major version upgrade from Spring Boot 2.2.5 to 3.2.0, which introduces significant and mandatory breaking changes. A dedicated migration effort is required before this upgrade can be merged.

Key Breaking Changes:

• Java 17 Baseline Required: Spring Boot 3.x requires Java 17 or later. Applications must be upgraded from older JDK versions (like 8 or 11) to run.
• Migration to Jakarta EE: This is the largest breaking change. Spring Boot 3.x has migrated from Java EE to Jakarta EE. All javax.* package imports in your code must be manually refactored to jakarta.*. For example, javax.servlet.http.HttpServletRequest becomes jakarta.servlet.http.HttpServletRequest. Your application will not compile without these changes.
• Jetty 12 Upgrade: This starter now uses Jetty 12, which supports the Jakarta Servlet 6.0 API. The previous version used Jetty 9. Any custom server configurations or direct interactions with the embedded Jetty server will likely need to be updated.
• Configuration Property Changes: Numerous configuration properties have been renamed or removed. For example, server.max.http.header.size is now server.max-http-request-header-size. It is recommended to use the spring-boot-properties-migrator module to help identify and migrate deprecated properties.

Recommendation:

This upgrade cannot be completed without significant code and environment changes. Follow the official Spring Boot 3.0 migration guide. The recommended path is to first upgrade to the latest Spring Boot 2.7.x release, address deprecations, and then perform the migration to 3.2.0.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}