From 7579a80a307d8fbc828573697ff629349765f58b Mon Sep 17 00:00:00 2001
From: Andreas Svanberg <andreas.svanberg@mensa.se>
Date: Mon, 22 Sep 2025 21:27:40 +0200
Subject: [PATCH] Remove hard dependency logger implementation `jcl-over-slf4j`

It should be up to the application to decide which logging implementation to use and where the various facades direct their logging.

The `<optional>` tag is not inherited from the `<dependencyManagement>` section in the parent POMs.

See https://github.com/apache/maven/issues/6974
See https://github.com/apache/maven/issues/6692
---
 jasperreports-parent/jasperreports/pom.xml | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/jasperreports-parent/jasperreports/pom.xml b/jasperreports-parent/jasperreports/pom.xml
index 7566b53965..dcefe94896 100644
--- a/jasperreports-parent/jasperreports/pom.xml
+++ b/jasperreports-parent/jasperreports/pom.xml
@@ -23,12 +23,6 @@
 			<artifactId>slf4j-api</artifactId>
 		</dependency>
 
-		<!-- Inherited -->
-		<dependency>
-			<groupId>org.slf4j</groupId>
-			<artifactId>jcl-over-slf4j</artifactId>
-		</dependency>
-
 		<!-- Module-specific -->
 		<dependency>
 			<groupId>net.sf.jasperreports</groupId>