I think the logging.log4j ones are expected as that is the switch from
the old log4j 1 to log4j 2.
Projects using commons.logging usually need to overwrite the package
import to use 1.2 as the base - as that is what slf4j exports.
On top I see org.slf4j.spi and org.apache.log4j (1.x) in the package
imports. The latter should have been fixed by the switch to 2.x. The
former shouldnt be there either.
@Julian Can you please look into these?
Regards
Carsten
On 2/12/2026 6:18 AM, Eric Norman wrote:
Just noticed that there appears to also be a new unresolved dependency
related to commons-logging as well (minimum 1.3 vs 1.2 provided by sling
commons log):
[ERROR] [bundle-packages] org.apache.sling:org.apache.sling.xss:2.4.10:
Bundle is importing package org.apache.commons.logging;version=[1.3,2) with
start order 20 but no bundle is exporting these for that start order in the
required version range.
Regards,
Eric
On Wed, Feb 11, 2026 at 8:48 PM Eric Norman <[email protected]> wrote:
Sorry, I missed this vote.
I do see when I try to update to this release it fails with unresolved
dependencies related to log4j. Was that expected?
[ERROR] [bundle-packages] org.apache.sling:org.apache.sling.xss:2.4.10:
Bundle is importing packages [org.apache.logging.log4j,
org.apache.logging.log4j.spi, org.apache.logging.log4j.util] with start
order 20 but no bundle is exporting these for that start order.
Regards,
Eric
On Tue, Feb 10, 2026 at 9:58 AM Julian Reschke <[email protected]> wrote:
Hi,
The vote has passed with the following result:
+1 (binding): Carsten Ziegeler, Robert Munteanu, Julian Reschke
I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.
Thanks for voting!
--
Carsten Ziegeler
Adobe
[email protected]
