[JIRA] (SLF4J-365) CLONE - Provide a BOM of all slf4j artifacts

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (SLF4J-365) CLONE - Provide a BOM of all slf4j artifacts

JIRA noreply-jira@qos.ch

    [ https://jira.qos.ch/browse/SLF4J-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18594#comment-18594 ]

Michael commented on SLF4J-365:
-------------------------------

Please start another try with a BOM.

 

Here is my version I'm using:
{code:java}
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">

<modelVersion>4.0.0</modelVersion>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-bom</artifactId>

<version>1.7.25</version>
<packaging>pom</packaging>
<url>http://www.slf4j.org</url>
<name>SLF4J BOM</name>

<licenses>
<license>
<name>MIT License</name>
<url>http://www.opensource.org/licenses/mit-license.php</url>
<distribution>repo</distribution>
</license>
</licenses>


<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>jcl-over-slf4j</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>jul-to-slf4j</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>log4j-over-slf4j</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>osgi-over-slf4j</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-jcl</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-jdk14</artifactId>
<version>${slf4j.version}</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-log4j12</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-simple</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-nop</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-ext</artifactId>
<version>${project.version}</version>
</dependency>
</dependencies>
</dependencyManagement>
</project>
{code}
Kind regards,

Michael

> 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
[hidden email]
http://mailman.qos.ch/mailman/listinfo/slf4j-dev
Loading...