
<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>com.metaobjects</groupId>
        <artifactId>metaobjects</artifactId>
        <version>7.4.1</version>
    </parent>

    <artifactId>metaobjects-om</artifactId>
    <packaging>jar</packaging>

    <name>MetaObjects :: ObjectManager</name>
    <url>https://github.com/metaobjectsdev/metaobjects</url>
    <description>MetaObjects for Model-driven development - ObjectManager</description>

    <dependencies>
        <dependency>
            <groupId>com.metaobjects</groupId>
            <artifactId>metaobjects-metadata</artifactId>
        </dependency>
        <!--
            Runtime extract engine (ExtractSchema / FieldSpec / Extract). The render
            module is zero-core-dependency by design (it cannot see MetaObject), so the
            metadata->ExtractSchema bridge + object-graph assembly (Phase B runtime
            extract) is sited HERE, in the ObjectManager runtime, which sits above both
            metadata and render and is the natural home for a runtime API (NOT codegen).
        -->
        <dependency>
            <groupId>com.metaobjects</groupId>
            <artifactId>metaobjects-render</artifactId>
            <version>${project.version}</version>
        </dependency>
        <!-- Test dependency for compliance test base classes -->
        <dependency>
            <groupId>com.metaobjects</groupId>
            <artifactId>metaobjects-metadata</artifactId>
            <version>${project.version}</version>
            <type>test-jar</type>
            <scope>test</scope>
        </dependency>

        <!-- JUnit for testing -->
        <dependency>
            <groupId>junit</groupId>
            <artifactId>junit</artifactId>
            <scope>test</scope>
        </dependency>
    </dependencies>

</project>
