Description

<dependency>
    <groupId>com.github.nruzic.playground.submodule.release</groupId>
    <artifactId>aggregator</artifactId>
    <version>2.0.2</version>
</dependency>

<?xml version="1.0" encoding="UTF-8"?>
<!-- Copyright -->
<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.github.nruzic.commons.master</groupId>
        <artifactId>nruzic-commons-master</artifactId>
        <version>3.0.0-RC16</version>
        <relativePath />
    </parent>

    <groupId>com.github.nruzic.playground.submodule.release</groupId>
    <artifactId>aggregator</artifactId>
    <version>2.0.2</version>
    <packaging>pom</packaging>
    <name>aggregator</name>

    <scm>
        <developerConnection>scm:git:file:///home/nruzic/git/nruzic/playground/aggregator.git</developerConnection>
        <tag>aggregator-2.0.2</tag>
    </scm>

    <build>
        <pluginManagement>
            <plugins>
                <plugin>
                    <groupId>org.apache.maven.plugins</groupId>
                    <artifactId>maven-release-plugin</artifactId>
                    <configuration>
                        <!-- this is a hack to trigger custom release profile
                            (not the one from master pom) during preparation step, in addition to execution
                            by perform step which is triggered by releaseProfiles tag -->
                        <arguments>-DreleaseTasks -Dbranch=${project-branch} -Dsettings.security=${settings-security} -N</arguments>
                    </configuration>
                </plugin>
            </plugins>
        </pluginManagement>
    </build>

    <modules>
        <module>submodule-1</module>
    </modules>
</project>