Description

<dependency>
    <groupId>io.github.ctgnz</groupId>
    <artifactId>fxtivity-core</artifactId>
    <version>1.0.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.ctgnz</groupId>
        <artifactId>fxtivity-parent</artifactId>
        <version>1.0.0</version>
        <relativePath>../fxtivity-parent/pom.xml</relativePath>
    </parent>

    <artifactId>fxtivity-core</artifactId>
    <packaging>jar</packaging>

    <name>fxtivity Core</name>
    <description>The Effectivity pattern on JavaFX: date-bounded entities, values that change over time, and observable collections that all follow one application-wide effective date.</description>
    <url>https://github.com/ctgnz/fxtivity</url>

    <dependencies>
        <!--
            javafx-base only - beans and collections, which is everything the effective date and the
            observable lists need. Nothing here starts a toolkit, so neither this library nor its tests
            need a display. The controls, which do, are a module of their own.
        -->
        <dependency>
            <groupId>org.openjfx</groupId>
            <artifactId>javafx-base</artifactId>
        </dependency>

        <!--
            Annotations only. The model declares how it is serialised, but nothing here serialises
            anything, so a consumer who never writes these objects out pays for no Jackson runtime.
        -->
        <dependency>
            <groupId>com.fasterxml.jackson.core</groupId>
            <artifactId>jackson-annotations</artifactId>
        </dependency>

        <!--
            Optional: it supplies @YamlFlowStyle, which keeps a time-varying value's history on one line
            per change when written as YAML. A consumer writing YAML with yaml-flock already has it; one
            writing JSON, or not serialising at all, should not inherit a YAML stack for an annotation
            it never reads. An annotation whose class is absent at runtime is simply ignored.
        -->
        <dependency>
            <groupId>io.github.ctgnz</groupId>
            <artifactId>yaml-flock</artifactId>
            <optional>true</optional>
        </dependency>

        <!-- The persistence tests round-trip models through YAML, so the tests need the writer. -->
        <dependency>
            <groupId>com.fasterxml.jackson.core</groupId>
            <artifactId>jackson-databind</artifactId>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>com.fasterxml.jackson.dataformat</groupId>
            <artifactId>jackson-dataformat-yaml</artifactId>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>com.fasterxml.jackson.datatype</groupId>
            <artifactId>jackson-datatype-jsr310</artifactId>
            <scope>test</scope>
        </dependency>

        <dependency>
            <groupId>org.junit.jupiter</groupId>
            <artifactId>junit-jupiter</artifactId>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>org.hamcrest</groupId>
            <artifactId>hamcrest</artifactId>
            <scope>test</scope>
        </dependency>
    </dependencies>

</project>