Skip to content

core : upgrade slf4j while still supporting aem customers  #225

@francoisledroff

Description

@francoisledroff

follow-up bug of #182

Maybe leave the top-level slf4j dependency version to be 2.x,
but the AEM sub-package parent pom overrides it downgraded to 1.x?

This way third party, non-aem uses can keep up-to-date, but the AEM bundles still deploy correctly to that context. Thoughts?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions