glogging-core
Used in:
components
- OverviewOverview
- VersionsVersions
- DependentsDependents
- DependenciesDependencies
<dependency>
<groupId>io.github.aaabramov</groupId>
<artifactId>glogging-core</artifactId>
<version>0.2.0</version>
</dependency><?xml version="1.0" encoding="UTF-8"?>
<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/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>io.github.aaabramov</groupId>
<artifactId>glogging</artifactId>
<version>0.2.0</version>
</parent>
<artifactId>glogging-core</artifactId>
<name>core</name>
<properties>
<!-- version.logback lives in the root pom: gson and jackson need it too. -->
<!--
Stable module name for JPMS consumers. Without it the JDK derives one
from the jar filename, which is both unstable and unchangeable later
without breaking every `requires` clause that guessed it.
-->
<module.name>io.github.aaabramov.glogging.core</module.name>
</properties>
<dependencies>
<!--
provided, not compile: this is an extension *to* logback, so the
application already has it. Exporting it as a compile dependency
pushed our 1.3.x onto every consumer, where it competes with
whatever logback they actually run - nearest-wins usually spares an
app on 1.5.x/1.6.x, but relying on that is not a design.
The version below is therefore a floor for compiling and testing
*this* project, not a version we ship to anyone.
-->
<dependency>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-core</artifactId>
<version>${version.logback}</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-classic</artifactId>
<version>${version.logback}</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.junit.jupiter</groupId>
<artifactId>junit-jupiter</artifactId>
<scope>test</scope>
</dependency>
</dependencies>
</project>