Tags make it easier to configure deployments by marking which deployables should be mapped to which containers.
<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/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>com.xebialabs.deployit</groupId> <artifactId>maven-deployit-plugin-dar-format</artifactId> <packaging>dar</packaging> <!-- DAR packaging --> <version>1.0</version> <name>Dar Format</name> <url>http://www.xebialabs.com</url> <build> <plugins> <plugin> <groupId>com.xebialabs.deployit</groupId> <artifactId>maven-deployit-plugin</artifactId> <version>3.9.2</version> <extensions>true</extensions> <!-- tells maven the plugin contains extensions --> <configuration> <deployables> <jee.War name="petclinic" groupId="com.xebialabs.deployit.demo.petclinic-war" artifactId="PetClinic"> <tags> <value>frontend</value> </tags> </jee.War> <jee.War name="petclinic-backend" groupId="com.xebialabs.deployit.demo.petclinic-war" artifactId="PetClinic-Backend"> <tags> <value>backend</value> </tags> </jee.War> <file.Archive name="mysql-backend" groupId="mysql" artifactId="mysql-connector-java"> <tags> <value>frontend</value> <value>backend</value> </tags> </file.Archive> </deployables> </configuration> </plugin> </plugins> </build> </project>