[Snyk] Security upgrade ch.qos.logback:logback-classic from 1.2.3 to 1.5.25

[ayusuf-mq]

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

Snyk changed the following file(s):

• modules/openapi-generator-cli/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.3 -> 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 major version upgrade introduces significant breaking changes, requiring updates to runtime dependencies, configurations, and potentially custom code. The upgrade spans from the end-of-life 1.2.x series to the 1.5.x series, incorporating all breaking changes from versions 1.3.x and 1.4.x.

Highlights:

• Java and SLF4J Upgrade Required: The target version 1.5.25 requires Java 11 (or newer) and SLF4J 2.0.x at runtime. Version 1.2.3 was compatible with older versions.
• Namespace change for EE components: Optional components like SMTPAppender have migrated from Java EE (javax.*) to Jakarta EE (jakarta.*) starting in version 1.4.x.

Other notable changes include the removal of Groovy configuration support, schema changes for DBAppender, and the removal of JaninoEventEvaluator for conditional configurations.

Source: Logback documentation
Recommendation: A direct upgrade is not recommended without careful planning. Developers must ensure their project is compatible with Java 11 and SLF4J 2.x. Configuration files, especially those using conditional logic or optional EE appenders, must be reviewed and tested. If using DBAppender, the database schema will need to be altered.

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