[Snyk] Fix for 1 vulnerabilities

[ayusuf-mq]

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

Snyk changed the following file(s):

• samples/server/petstore/jaxrs-datelib-j8/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	External Initialization of Trusted Variables or Data Stores SNYK-JAVA-CHQOSLOGBACK-15062482	290	ch.qos.logback:logback-classic: 1.2.0 -> 1.5.25 ch.qos.logback:logback-core: 1.2.0 -> 1.5.25 No Path Found No Known Exploit

---

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.

[ayusuf-mq]

This upgrade from 1.2.0 to 1.5.25 is a major update that crosses several Logback series and introduces significant breaking changes. It requires updates to core dependencies like Java and SLF4J, and includes breaking API and schema changes.

Highlights:

• Update runtime and dependencies: Logback 1.5.x requires Java 11 and SLF4J 2.0.x at runtime. [1] The 1.2.x series was compatible with older versions of Java and SLF4J 1.7.x, so you must upgrade the SLF4J API dependency across your project. [5]
• Check for breaking component changes: Optional components like SMTPAppender now depend on Jakarta EE (jakarta.*) instead of Java EE (javax.*). [2] Additionally, DBAppender requires a database schema change to add four new columns for arguments (arg0, arg1, arg2, arg3). [2]

Source: Logback documentation
Recommendation: Before merging, you must upgrade the SLF4J dependency to the 2.0.x series and ensure the project uses Java 11 or newer. Review configurations for any custom code interacting with Logback's internal Joran configuration system, as it was rewritten. [2] If using DBAppender, apply the necessary schema migration. [2]

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