fix: resolve SLF4J and Logback compatibility issues

[GOODBOY008]

Summary

This PR fixes the compatibility issue between logback-classic and slf4j-api, and removes the erroneous Spring Boot configuration from logback.xml.

Changes

1. Update logback-classic version (pom.xml)

• Changed `logback-classic.version` from `1.5.24` to `1.3.14`
• Logback 1.3.x is the last version compatible with Java 8 (while supporting SLF4J 2.x)
• Logback 1.4.x/1.5.x requires Java 11+

2. Update slf4j-api version (pom.xml)

• Changed `slf4j-api.version` from `1.7.36` to `2.0.17`
• SLF4J 2.0.x is compatible with Java 8+ and works with Logback 1.3.x

3. Replace log bridging dependencies (pom.xml)

• Replaced `slf4j-simple`, `jcl-over-slf4j`, `log4j-over-slf4j` with `log4j-to-slf4j`
• Simplifies the logging configuration and avoids binding conflicts

4. Fix logback.xml configuration

• Removed `<include resource="org/springframework/boot/logging/logback/defaults.xml"/>` (not available in test classpath)
• Added explicit log pattern definition
• Changed root log level from `DEBUG` to `INFO` for cleaner test output
• Added POI logger configuration to reduce noise

Compatibility Matrix

Component	Version	Java Compatibility
slf4j-api	2.0.17	Java 8+
logback-classic	1.3.14	Java 8+
logback-core	1.3.14	Java 8+

[Copilot]

Pull request overview

This PR addresses SLF4J and Logback compatibility issues by removing the slf4j-simple binding in favor of logback-classic and fixing Logback configuration files to remove Spring Boot-specific elements that are not supported in standard Logback.

Key changes:

• Removed slf4j-simple dependency and its version property from the parent POM
• Downgraded logback-classic version from 1.5.23 to 1.2.13
• Updated fesod-sheet test logback configuration to use standard Logback properties instead of Spring Boot includes

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
pom.xml	Removed slf4j-simple dependency and version property, downgraded logback-classic version to 1.2.13, and removed slf4j-simple from parent dependencies
fesod-sheet/src/test/resources/logback.xml	Replaced Spring Boot logback include with standard property definition and changed root log level from DEBUG to INFO

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[GOODBOY008]

@alaahong @delei lei PTAL

[alaahong]

why not upgrade to slf4j 2.x ?
And meanwhile, can you also attach the screenshot of actual execution log?

[GOODBOY008]

@alaahong It’s fine for me to upgrade SLF4J to 2.x, as long as we can reach a consensus.Considered both options—upgrading SLF4J and staying with SLF4J 1.7.x. To minimize risk and scope of change, I chose the minimal-change approach by downgrading logback-classic.

Issue：

Compatibility Issue

• Logback 1.5.x requires SLF4J 2.0.x, but this project uses SLF4J 1.7.36

Redundant Issue

• The project has both slf4j-simple and logback-classic as test dependencies,slf4j-simple and logback-classic are competing SLF4J implementations

Log output in console (Before)

Log output in console (Remove slf4j-simple)

Log output in console (Apply the current pr)

[GOODBOY008]

@alaahong PR updated. SLF4J has been upgraded to 2.x, and logback-classic has been downgraded to 1.3.x to maintain Java 8 compatibility.

Reference：

Java Logging Part 2: Logging and Package Exclusion with SLF4J + Logback

[GOODBOY008]

@delei PTAL,If you have time, Thank you~

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

This module explicitly uses Logback 1.2.13 which requires SLF4J 1.7.x, but the parent POM now defines slf4j-api.version as 2.0.17 (line 73 in parent pom.xml). This creates a version conflict:

• Logback 1.2.13 depends on SLF4J 1.7.x
• Parent POM declares SLF4J 2.0.17

Since this module excludes slf4j-api from spring-boot-starter-web (line 52-54) and relies on the parent's SLF4J version, there will be a runtime incompatibility. Either:

1. Keep Logback 1.2.13 and explicitly declare slf4j-api 1.7.36 as a dependency in this module, OR
2. Upgrade to Logback 1.3.14 to match the parent POM's SLF4J 2.0.17 (but note this may conflict with Spring Boot 2.7.18's expectations)

Suggested change

	</dependency>
	</dependency>
	<!-- Explicitly use SLF4J 1.7.x to match Logback 1.2.13 and avoid SLF4J 2.0.x from parent -->
	<dependency>
	<groupId>org.slf4j</groupId>
	<artifactId>slf4j-api</artifactId>
	<version>1.7.36</version>
	<scope>test</scope>
	</dependency>

[Copilot]

The comment states "Use Logback 1.2.x with SLF4J 1.7.x for Spring Boot 2.7.x compatibility" but the parent POM (line 73) now declares slf4j-api version 2.0.17, not 1.7.x. Since this module excludes slf4j-api from spring-boot-starter-web and doesn't explicitly declare its own slf4j-api dependency, it will inherit version 2.0.17 from the parent, making the comment inaccurate. Either update the comment to reflect the actual configuration or add an explicit slf4j-api 1.7.36 dependency to match the comment's intent.

Suggested change

	<!-- Use Logback 1.2.x with SLF4J 1.7.x for Spring Boot 2.7.x compatibility -->
	<!-- Use Logback 1.2.x; SLF4J version is inherited from the parent POM (currently 2.0.17) -->