[
https://jira.qos.ch/browse/SLF4J-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19364#comment-19364
]
Jörg Sesterhenn commented on SLF4J-365:
---------------------------------------
Please vote for SLF4J-437 if you want this feature. It's a duplicate issue that
is not yet closed ;).
> CLONE - Provide a BOM of all slf4j artifacts
> --------------------------------------------
>
> Key: SLF4J-365
> URL: https://jira.qos.ch/browse/SLF4J-365
> Project: SLF4J
> Issue Type: New Feature
> Reporter: Ceki Gülcü
> Assignee: Ceki Gülcü
> Fix For: 1.7.22
>
>
> We have an enterprise parent POM that defines versions of maven artifacts for
> all products that are built in our enterprise.
> We want to define the version of all slf4j artifacts in that parent pom.
> Idealy we would just import a BOM
> (https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html).
> Instead of importing your BOM we now list all slf4j modules in our parent
> POM. Which means we have to check for new/changed modules with every version.
> One example of a great BOM is [the log4j
> BOM|http://central.maven.org/maven2/org/apache/logging/log4j/log4j-bom/2.5/log4j-bom-2.5.pom].
> Please provide a BOM just like Log4j2 does, so that we can import it in our
> enterprise parent pom.
--
This message was sent by Atlassian JIRA
(v7.3.1#73012)
_______________________________________________
slf4j-dev mailing list
[email protected]
http://mailman.qos.ch/mailman/listinfo/slf4j-dev
