Description

<dependency>
    <groupId>global.namespace.truelicense</groupId>
    <artifactId>truelicense-obfuscate</artifactId>
    <version>4.1.4</version>
</dependency>

<?xml version='1.0'?>
<!--
  ~ Copyright (C) 2005 - 2019 Schlichtherle IT Services.
  ~ All rights reserved. Use is subject to license terms.
  -->
<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>global.namespace.truelicense</groupId>
        <artifactId>truelicense</artifactId>
        <version>4.1.4</version>
    </parent>

    <artifactId>truelicense-obfuscate</artifactId>

    <name>TrueLicense @Obfuscate</name>
    <description>
        The TrueLicense @Obfuscate module provides core functionality for
        obfuscating constant string values in Java source and class files.
    </description>

    <properties>
        <automatic.module.name>global.namespace.truelicense.obfuscate</automatic.module.name>
    </properties>

    <build>
        <plugins>
            <plugin>
                <artifactId>maven-compiler-plugin</artifactId>
                <configuration>
                    <proc>none</proc>
                </configuration>
            </plugin>
            <plugin>
                <!--
                  ~ Must be spelled exactly as in the root POM's <pluginManagement>: Maven matches a plugin against
                  ~ its management entry by the *raw*, un-interpolated groupId, so the literal group id would not
                  ~ pick up the managed version and the build would warn that the version is missing.
                  -->
                <groupId>${project.groupId}</groupId>
                <artifactId>truelicense-maven-plugin</artifactId>
                <executions>
                    <!--
                      ~ Repeated from the enable-obfuscate-main-classes profile in the root POM on purpose: declaring
                      ~ this plugin in a module suppresses the profile-injected execution instead of merging with it,
                      ~ so without this the module would silently not get obfuscated. Any other module that declares
                      ~ this plugin must repeat it too.
                      -->
                    <execution>
                        <id>obfuscate-main-classes</id>
                        <goals>
                            <goal>obfuscate-main-classes</goal>
                        </goals>
                    </execution>
                    <execution>
                        <id>generate-main-sources</id>
                        <goals>
                            <goal>generate-main-sources</goal>
                        </goals>
                    </execution>
                    <execution>
                        <id>generate-test-sources</id>
                        <goals>
                            <goal>generate-test-sources</goal>
                        </goals>
                        <configuration>
                            <templateSets>
                                <set>
                                    <directory>src/test/scala</directory>
                                    <includes>
                                        <include>**/*.vtl</include>
                                    </includes>
                                </set>
                            </templateSets>
                        </configuration>
                    </execution>
                </executions>
            </plugin>
        </plugins>
    </build>
</project>