[ https://jira.qos.ch/browse/SLF4J-437?page=com.atlassian.jira.plugin.system.i... ] Jörg Sesterhenn commented on SLF4J-437: --------------------------------------- @Joachim, @Michael please be nice to one another :) I have described our usecase in https://jira.qos.ch/browse/SLF4J-365 which got closed as won't fix for beeing to much effort. I believe Ceki already sees the value of that feature for users of slf4j (at least he stated it makes sense in LOGBACK-1157). By providing examples and an alternative implementation I hope to have lowered the burden of creating an initial BOM. Maybe if more users see the value in BOMs this issue will get somewhere. @Joachim: Let me explain the advantage of a BOM for us with an example: ------------------------------------------------------------------------------------------------------- Example: slf4j adds another module, or renames a module. Without BOM every project will have to carefully read the releasenotes and then add another entry to their (parent-)pom where the slf4js modules are listed and add/rename a module. In big companys this might be centralized so that you have to do this for a lot of libraries. It's a tedious and error prone task. With BOM every project just raises the version of the BOM in the (parent-)pom to the latest and automatically ensures that all module versions are managed. This is quite convenient and also helps to keep our parent-pom at a somewhat manageable size. There are more examples like just increasing the version, or dropping a module where the same logic applies. @Joachim: Did this help? ------------------------------------------------------------------------------------------------------- Slf4j still needs to deal with the housekeeping of its BOM (best integrate it into the build process) - which is essentially what other companys/teams gain from having a single BOM for a library - less housekeeping. It would simply make an awesome library just a little bit more awesome ;)

Create a BOM POM ----------------

Key: SLF4J-437 URL: https://jira.qos.ch/browse/SLF4J-437 Project: SLF4J Issue Type: Task Affects Versions: 1.8.0-beta2 Reporter: Michael Osipov Assignee: SLF4J developers list

Please create a {{slf4j-bom}} POM which can be imported via dependency management. This makes consumer POM less verbose, no need to repeat version. The Spring Framework does this for example.

-- This message was sent by Atlassian JIRA (v7.3.1#73012)