[ https://jira.qos.ch/browse/SLF4J-437?page=com.atlassian.jira.plugin.system.… ]
Jörg Sesterhenn commented on SLF4J-437:
---------------------------------------
For an example see: [https://github.com/eonian-technologies/slf4j-bom/blob/master/pom.xml]
I would rather use a bom provided by the project itself, than a bom by someone else.
There is another example in https://jira.qos.ch/browse/SLF4J-365
Please reconsider. Many widely used Frameworks (with more than one module) provide a BOM (log4j, spring, arquillian, weld, deltaspike,...). It is important to us and will ease dependency management.
> 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)
Pavel_K created SLF4J-447:
-----------------------------
Summary: Slf4j-ext contains package org.slf4j
Key: SLF4J-447
URL: https://jira.qos.ch/browse/SLF4J-447
Project: SLF4J
Issue Type: Bug
Components: slf4j-ext
Affects Versions: 1.8.0-beta2
Reporter: Pavel_K
Assignee: SLF4J developers list
Slf4j-ext includes package org.slf4j (class org.slf4j.NDC) what is a serious problem if we use slf4j with JPMS. For example, we can't build log4j-slf4j18-impl for JPMS because it uses both slf4j-api and slf4j-ext and both these modules export the same package - org.slf4j.
--
This message was sent by Atlassian JIRA
(v7.3.1#73012)
