Usage

This page provides general usage information. The Deployit Maven plugin has two main usages:

  • to create a Deployit Deployment package including artefacts, managed in pom.xml file or a maven repository, and file sets corresponding to configuration files, SQL Files, static contents... A new packaging type has been added, dar, to provide a dedicated lifecycle and to produce new kind of archive, dar files - Deployment Archive. These dar files could be used to be deployed within the maven plugin or to be imported into a Deployit server directly from a enterprise maven repository (eg. Artifactory, Nexus,....)
  • to deploy Deployit Deployment package to an environment in order to, for example, run a set of tests (functional tests, technical tests, performance tests). This is done during the pre-integration-test and pre-integration-test phase. This is done using deployit:deploy goal. The deployit:clean undeploys the current deployment package.

Getting started with Deployit Maven plugin

To use the Deployit maven plugin, you need to:

  • Add the XebiaLabs repository to your pom.xm
          <pluginRepositories>
          ...
            <pluginRepository>
                <id>nexus-dexter-releases</id>
                <url>http://nexus.xebialabs.com/nexus/content/repositories/releases</url>
            </pluginRepository>
    
            <pluginRepository>
                <id>nexus-dexter-snapshots</id>
                <url>http://nexus.xebialabs.com/nexus/content/repositories/snapshots</url>
            </pluginRepository>
        ....
        </pluginRepositories>
  • Add the maven plugin credentials to your settings.xml file.
        <servers>
        ...
            <server>
                <id>nexus-dexter-releases</id>
                <username>username</username>
                <password>password</password>
            </server>
            <server>
                <id>nexus-dexter-snapshots</id>
                <username>username</username>
                <password>password</password>
            </server>
        ...
        </servers>