You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2026/05/13 10:45:00 UTC

[jira] [Updated] (CAMEL-23498) Cleanup remaining SLF4J 1.x artifacts after upgrade to 2.0.x

     [ https://issues.apache.org/jira/browse/CAMEL-23498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-23498:
--------------------------------
    Component/s: build system
                     (was: camel-core)

> Cleanup remaining SLF4J 1.x artifacts after upgrade to 2.0.x
> ------------------------------------------------------------
>
>                 Key: CAMEL-23498
>                 URL: https://issues.apache.org/jira/browse/CAMEL-23498
>             Project: Camel
>          Issue Type: Improvement
>          Components: build system
>            Reporter: Claus Ibsen
>            Priority: Minor
>             Fix For: 4.21.0
>
>
> The project upgraded from SLF4J 1.7.x to 2.0.x in CAMEL-18932, but some remnants were missed:
> h3. 1. log4j-slf4j-impl should be log4j-slf4j2-impl (9 modules)
> These modules use the old SLF4J 1.x Log4j2 binding ({{log4j-slf4j-impl}}) as a test dependency instead of the SLF4J 2.x variant ({{log4j-slf4j2-impl}}):
> - camel-zeebe
> - camel-parquet-avro
> - camel-flowable
> - camel-optaplanner
> - camel-solr
> - camel-datasonnet
> - camel-swift
> - camel-camunda
> - camel-pulsar
> Two more modules (camel-milvus, camel-kudu) exclude {{log4j-slf4j-impl}} from transitive deps — those exclusions are harmless but stale.
> h3. 2. Hardcoded jcl-over-slf4j 1.7.36 in camel-launcher
> {{dsl/camel-jbang/camel-launcher/pom.xml}} pins {{jcl-over-slf4j}} to version 1.7.36 instead of using {{$\{slf4j-version\}}}.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)