ci.maven

Collection of Maven plugins and archetypes for managing WebSphere Application Server Liberty Profile and applications.

• Build
• Plugins
• liberty-maven-plugin
  • Configuration
  • Goals
    • install-server
    • create-server
    • start-server
    • run-server
    • stop-server
    • package-server
    • clean-server
    • dump-server
    • java-dump-server
    • deploy
    • undeploy
    • install-feature
    • uninstall-feature
    • install-apps
• Packaging types
• liberty-assembly
• Archetypes
• liberty-plugin-archetype

Build

Use Maven 2.x or 3.x to build the Liberty plugins and archetypes.

• mvn install : builds the plugin and the archetype.
• mvn install -Poffline-its -DwlpInstallDir=<liberty_install_directory> : builds the plugin, archetype and runs the integration tests by providing an existing installation.
• mvn install -Ponline-its -DwlpVersion=<liberty_version> -DwlpLicense=<liberty_license_code> : builds the plugin, archetype and runs the integration tests by downloading a new server.
  • Liberty versions and their respective link to the license code can be found in the index.yml file. You can obtain the license code by reading the current license and looking for the D/N: line.

Plugins

liberty-maven-plugin

liberty-maven-plugin provides a number of goals for managing Liberty Profile server and applications.

Configuration

To enable liberty-maven-plugin in your project add the following to your pom.xml:

<project>
    ...
    <build>
        <plugins>
            <!-- Enable liberty-maven-plugin -->
            <plugin>
                <groupId>net.wasdev.wlp.maven.plugins</groupId>
                <artifactId>liberty-maven-plugin</artifactId>
                <version>1.1</version>
                <!-- Specify configuration, executions for liberty-maven-plugin -->
                ...
            </plugin>
        </plugins>
    </build>
    ...
</project>

If you are using a snapshot version of liberty-maven-plugin then you will also need to add the following plugin repository to your pom.xml:

<project>
    ...
    <pluginRepositories>
        <!-- Configure Sonatype OSS Maven snapshots repository -->
        <pluginRepository>
            <id>sonatype-nexus-snapshots</id>
            <name>Sonatype Nexus Snapshots</name>
            <url>https://oss.sonatype.org/content/repositories/snapshots/</url>
            <snapshots>
                <enabled>true</enabled>
            </snapshots>
            <releases>
                <enabled>false</enabled>
            </releases>
        </pluginRepository>
    </pluginRepositories>
    ...
</project>

Liberty installation configuration

liberty-maven-plugin must first be configured with Liberty profile installation information. The installation information can be specified as an existing installation directory, a packaged server, or as a Maven artifact. The liberty-maven-plugin can also download and install Liberty profile server from the Liberty repository or other location. By default, the plugin will install Liberty runtime with the Java EE 7 Web Profile features from the Liberty repository.

Using an existing installation

Use the installDirectory parameter to specify the directory of an existing Liberty profile server installation. For example:

<plugin>
    <groupId>net.wasdev.wlp.maven.plugins</groupId>
    <artifactId>liberty-maven-plugin</artifactId>
    <configuration>
        <installDirectory>/opt/ibm/wlp</installDirectory>
    </configuration>
</plugin>

Using a packaged server

Use the assemblyArchive parameter to specify a packaged server archive (created using server package command) that contains Liberty profile server files. For example:

<plugin>
    <groupId>net.wasdev.wlp.maven.plugins</groupId>
    <artifactId>liberty-maven-plugin</artifactId>
    <configuration>
        <assemblyArchive>/opt/ibm/wlp.zip</assemblyArchive>
    </configuration>
</plugin>

Using Maven artifact

Use the assemblyArtifact parameter to specify the name of the Maven artifact that contains a custom Liberty profile server or use one of the provided on the Maven Central repository.

The Maven Central repository includes the following Liberty runtime artifacts:

Artifact ID	Versions	Description
wlp-javaee7	8.5.5.8, 8.5.5.7, 8.5.5.6	Liberty runtime with all Java EE 7 Full Platform features.
wlp-webProfile7	8.5.5.8, 8.5.5.7, 8.5.5.6	Liberty runtime with Java EE 7 Web Profile features.
wlp-kernel	8.5.5.8	Liberty runtime kernel.

Note: The group ID for these artifacts is: com.ibm.websphere.appserver.runtime.

Example for using the assemblyArtifact parameter:

<plugin>
    <groupId>net.wasdev.wlp.maven.plugins</groupId>
    <artifactId>liberty-maven-plugin</artifactId>
    <configuration>
        <assemblyArtifact>
            <groupId>com.ibm.websphere.appserver.runtime</groupId>
            <artifactId>wlp-webProfile7</artifactId>
            <version>8.5.5.7</version>
            <type>zip</type>
        </assemblyArtifact>
    </configuration>
</plugin>

Using a repository

Use the install parameter to download and install Liberty profile server from the Liberty repository or other location.

In certain cases, the Liberty license code may need to be provided in order to install the runtime. If the license code is required and if you are installing Liberty from the Liberty repository, you can obtain the license code by reading the current license and looking for the D/N: <license code> line. Otherwise, download the Liberty runtime archive and execute java -jar wlp*runtime.jar --viewLicenseInfo command and look for the D/N: <license code> line.

• Install from the Liberty repository. The plugin will use the Liberty repository to find the Liberty runtime archive to install based on the given version and type. This is the default installation method - no extra configuration is required. By default, the latest Liberty runtime with the Java EE 7 Web Profile features will be installed.

   <plugin>
       <groupId>net.wasdev.wlp.maven.plugins</groupId>
       <artifactId>liberty-maven-plugin</artifactId>
   </plugin>

• Install Liberty runtime with Java EE 6 Web Profile features from the Liberty repository (must provide licenseCode).

   <plugin>
       <groupId>net.wasdev.wlp.maven.plugins</groupId>
       <artifactId>liberty-maven-plugin</artifactId>
       <configuration>
           <install>
               <type>webProfile6</type>
               <licenseCode><license code></licenseCode>
           </install>
       </configuration>
   </plugin>

• Install from a given location. The runtimeUrl sub-parameter specifies a location of the Liberty profile's runtime .jar or .zip file to install. The licenseCode is only needed when installing from .jar file.

   <plugin>
       <groupId>net.wasdev.wlp.maven.plugins</groupId>
       <artifactId>liberty-maven-plugin</artifactId>
       <configuration>
           <install>
               <runtimeUrl><url to .jar or .zip file></runtimeUrl>
               <licenseCode><license code></licenseCode>
           </install>
       </configuration>
   </plugin>

The install parameter has the following sub-parameters:

Name	Description	Required
licenseCode	Liberty profile license code. See above.	Yes, if type is webProfile6 or runtimeUrl specifies a .jar file.
version	Exact or wildcard version of the Liberty profile server to install. Available versions are listed in the index.yml file. Only used if runtimeUrl is not set. The default value is 8.5.+.	No
type	Liberty runtime type to download from the Liberty repository. Currently, the following types are supported: kernel, webProfile6, webProfile7, and javaee7. Only used if runtimeUrl is not set. Defaults to webProfile6 if licenseCode is set and webProfile7 otherwise.	No
runtimeUrl	URL to the Liberty profile's runtime .jar or a .zip file. If not set, the Liberty repository will be used to find the Liberty runtime archive.	No
cacheDirectory	The directory used for caching downloaded files such as the license or .jar files. The default value is ${settings.localRepository}/wlp-cache.	No
username	Username needed for basic authentication.	No
password	Password needed for basic authentication.	No
serverId	Id of the server definition with the username and password in the ~/.m2/settings.xml file. Used for basic authentication.	No
maxDownloadTime	Maximum time in seconds the download can take. The default value is 0 (no maximum time).	No

---

Goals

Common Parameters

Parameters shared by all goals.

Parameter	Description	Required
installDirectory	Local installation directory of the Liberty profile server.	Yes, only when assemblyArchive, assemblyArtifact, and install parameters are not set.
assemblyArchive	Location of the Liberty profile server compressed archive. The archive will be unpacked into a directory as specified by the assemblyInstallDirectory parameter.	Yes, only when installDirectory, assemblyArtifact, and install parameters are not set.
assemblyArtifact	Maven artifact name of the Liberty profile server assembly. The assembly will be installed into a directory as specified by the assemblyInstallDirectory parameter.	Yes, only when installDirectory, assemblyArchive, and install parameters are not set.
install	Install Liberty runtime from the Liberty repository.	Yes, only when installDirectory, assemblyArchive, and assemblyArtifact parameters are not set.
serverName	Name of the Liberty profile server instance. The default value is defaultServer.	No
userDirectory	Alternative user directory location that contains server definitions and shared resources (WLP_USER_DIR).	No
outputDirectory	Alternative location for server generated output such as logs, the workarea directory, and other generated files (WLP_OUTPUT_DIR).	No
assemblyInstallDirectory	Local installation directory location of the Liberty profile server when the server is installed using the assembly archive, assembly artifact or repository option. The default value is ${project.build.directory}/liberty.	No
refresh	If true, re-install Liberty profile server into the local directory. This is only used when when the server is installed using the assembly archive or artifact option. The default value is false.	No
skip	If true, the specified goal is bypassed entirely. The default value is false.	No

Common Server Parameters

Additional parameters shared by all server-based goals.

Parameter	Description	Required
configFile	Location of a server configuration file to be used by the instance. The default value is ${basedir}/src/test/resources/server.xml.	No
bootstrapProperties	List of bootstrap properties for the server instance.	No
bootstrapPropertiesFile	Location of a bootstrap properties file to be used by the instance. The default value is ${basedir}/src/test/resources/bootstrap.properties.	No
jvmOptions	List of JVM options for the server instance.	No
jvmOptionsFile	Location of a JVM options file to be used by the instance. The default value is ${basedir}/src/test/resources/jvm.options.	No
serverEnv	Location of a server environment file to be used by the instance. The default value is ${basedir}/src/test/resources/server.env	No

Example:

<plugin>
    <groupId>net.wasdev.wlp.maven.plugins</groupId>
    <artifactId>liberty-maven-plugin</artifactId>
    <executions>
        ...
        <execution>
            <id>start-server</id>
            <phase>pre-integration-test</phase>
            <goals>
                <goal>start-server</goal>
            </goals>
            <configuration>
                <configFile>${project.build.testOutputDirectory}/wlp/server.xml</configFile>
                <bootstrapProperties>
                    <httpPort>8080</httpPort>
                </bootstrapProperties>
                <jvmOptions>
                    <param>-Xmx768m</param>
                </jvmOptions>
            </configuration>
        </execution>
        ...
    </executions>
</plugin>

install-server

---

Installs Liberty profile runtime. This goal is implicitly invoked by all the other plugin goals and usually does not need to be executed explicitly. However, there might be cases where explicit execution might be needed.

This goal only supports the common parameters.

Example:

<plugin>
    <groupId>net.wasdev.wlp.maven.plugins</groupId>
    <artifactId>liberty-maven-plugin</artifactId>
    <executions>
        ...
        <execution>
            <id>install-server</id>
            <phase>pre-integration-test</phase>
            <goals>
                <goal>install-server</goal>
            </goals>
            <configuration>
                <install>
                    <type>javaee7</type>
                </install>
            </configuration>
        </execution>
        ...
    </executions>
</plugin>

start-server

---

Start a Liberty Profile server in background. The server instance will be automatically created if it does not exist.

Additional Parameters

The following are the parameters supported by this goal in addition to the common server parameters and the common parameters.

Parameter	Description	Required
clean	Clean all cached information on server start up. The default value is false.	No
serverStartTimeout	Maximum time to wait (in seconds) to verify that the server has started. The default value is 30 seconds.	No
verifyTimeout	Maximum time to wait (in seconds) to verify that the applications have started. This timeout only has effect if the applications parameter is set. The default value is 30 seconds.	No
applications	A comma-separated list of application names to wait for during server start-up.	No

Example:

<plugin>
    <groupId>net.wasdev.wlp.maven.plugins</groupId>
    <artifactId>liberty-maven-plugin</artifactId>
    <executions>
        ...
        <execution>
            <id>start-server</id>
            <phase>pre-integration-test</phase>
            <goals>
                <goal>start-server</goal>
            </goals>
            <configuration>
                <verifyTimeout>60</verifyTimeout>
                <configFile>${project.build.testOutputDirectory}/wlp/server.xml</configFile>
            </configuration>
        </execution>
        ...
    </executions>
    <configuration>
       <installDirectory>/opt/ibm/wlp</installDirectory>
       <serverName>test</serverName>
    </configuration>
</plugin>

run-server

---

Start a Liberty Profile server in foreground. The server instance will be automatically created if it does not exist. Note: This goal is designed to be executed directly from the Maven command line.

Additional Parameters

The following are the parameters supported by this goal in addition to the common server parameters and the common parameters.

Parameter	Description	Required
clean	Clean all cached information on server start up. The default value is false.	No

Example:

<plugin>
    <groupId>net.wasdev.wlp.maven.plugins</groupId>
    <artifactId>liberty-maven-plugin</artifactId>
    <configuration>
       <installDirectory>/opt/ibm/wlp</installDirectory>
       <serverName>test</serverName>
    </configuration>
</plugin>

$ mvn liberty:run-server

stop-server

---

Stop a Liberty Profile server. The server instance must exist and must be running.

Additional Parameters

The following are the parameters supported by this goal in addition to the common server parameters and the common parameters.

Parameter	Description	Required
serverStopTimeout	Maximum time to wait (in seconds) to verify that the server has stopped. The default value is 30 seconds.	No

Example:

<plugin>
    <groupId>net.wasdev.wlp.maven.plugins</groupId>
    <artifactId>liberty-maven-plugin</artifactId>
    <executions>
        ...
        <execution>
            <id>stop-server</id>
            <phase>post-integration-test</phase>
            <goals>
                <goal>stop-server</goal>
            </goals>
            <configuration>
                <serverStopTimeout>60</serverStopTimeout>
            </configuration>
        </execution>
        ...
    </executions>
    <configuration>
       <installDirectory>/opt/ibm/wlp</installDirectory>
       <serverName>test</serverName>
    </configuration>
</plugin>

create-server

---

Create a Liberty Profile server.

Additional Parameters

The following are the parameters supported by this goal in addition to the common server parameters and the common parameters.

Parameter	Description	Required
template	Name of the template to use when creating a new server.	No

Example:

<plugin>
    <groupId>net.wasdev.wlp.maven.plugins</groupId>
    <artifactId>liberty-maven-plugin</artifactId>
    <executions>
        ...
        <execution>
            <id>create-server</id>
            <phase>pre-integration-test</phase>
            <goals>
                <goal>create-server</goal>
            </goals>
        </execution>
        ...
    </executions>
    <configuration>
       <installDirectory>/opt/ibm/wlp</installDirectory>
       <serverName>test</serverName>
    </configuration>
</plugin>

package-server

---

Package a Liberty Profile server.

Additional Parameters

The following are the parameters supported by this goal in addition to the common server parameters and the common parameters.

Parameter	Description	Required
packageFile	Location of the target file or directory. If the target location is a file, the contents of the server instance will be compressed into the specified file. If the target location is a directory, the contents of the server instance will be compressed into ${packageFile}/${serverName}.zip file. If the target location is not specified, it defaults to ${installDirectory}/usr/servers/${serverName}.zip if installDirectory is set. Otherwise, it defaults to ${assemblyInstallDirectory}/usr/servers/${serverName}.zip if assemblyArchive or assemblyArtifact is set.	No
include	Packaging type. One of all, usr, or minify. The default value is all.	Yes, only when the os option is set
os	A comma-delimited list of operating systems that you want the packaged server to support. To specify that an operating system is not to be supported, prefix it with a minus sign ("-"). The 'include' attribute must be set to 'minify'.	No

Example:

<plugin>
    <groupId>net.wasdev.wlp.maven.plugins</groupId>
    <artifactId>liberty-maven-plugin</artifactId>
    <executions>
        ...
        <execution>
            <id>package-server</id>
            <phase>package</phase>
            <goals>
                <goal>package-server</goal>
            </goals>
            <configuration>
                <packageFile>${project.build.directory}/test.zip</packageFile>
            </configuration>
        </execution>
        ...
    </executions>
    <configuration>
       <installDirectory>/opt/ibm/wlp</installDirectory>
       <serverName>test</serverName>
    </configuration>
</plugin>

clean-server

---

Deletes every file in the ${outputDirectory}/logs, ${outputDirectory}/workarea, ${userDirectory}/dropins or ${userDirectory}/apps.

Additional Parameters

Parameter	Description	Required
cleanLogs	Delete all the files in the ${outputDirectory}/logs directory. The default value is true.	No
cleanWorkarea	Delete all the files in the ${outputDirectory}/workarea directory. The default value is true.	No
cleanDropins	Delete all the files in the ${userDirectory}/dropins directory. The default value is false.	No
cleanApps	Delete all the files in the ${userDirectory}/apps directory. The default value is false.	No

Examples

Remove every app deployed to the ${userDirectory}/dropins and every file in the ${outputDirectory}/workarea and ${outputDirectory}/logs directories.

<project>
    ...
    <build>
        <plugins>
            <plugin>
                <groupId>net.wasdev.wlp.maven.plugins</groupId>
                <artifactId>liberty-maven-plugin</artifactId>
                <executions>
                    ...
                    <execution>
                        <id>clean</id>
                        <phase>post-integration-test</phase>
                        <goals>
                            <goal>clean-server</goal>
                        </goals>
                        <configuration>
                            <cleanDropins>true</dropins>
                        </configuration>
                    </execution>
                    ...
                </executions>
                <configuration>
                   <installDirectory>/opt/ibm/wlp</installDirectory>
                   <serverName>test</serverName>
                </configuration>
            </plugin>
        </plugins>
    </build>
    ...
</project>

dump-server

---

Dump diagnostic information from the server into an archive.

Additional Parameters

The following are the parameters supported by this goal in addition to the common server parameters and the common parameters.

Parameter	Description	Required
archive	Location of the target archive file.	No
systemDump	Include system dump information. The default value is false.	No
heapDump	Include heap dump information. The default value is false.	No
threadDump	Include thread dump information. The default value is false.	No

Example:

<plugin>
    <groupId>net.wasdev.wlp.maven.plugins</groupId>
    <artifactId>liberty-maven-plugin</artifactId>
    <executions>
        ...
        <execution>
            <id>dump-server</id>
            <phase>post-integration-test</phase>
            <goals>
                <goal>dump-server</goal>
            </goals>
            <configuration>
                <archive>${project.build.directory}/dump.zip</archive>
                <heapDump>true</heapDump>
            </configuration>
        </execution>
        ...
    </executions>
    <configuration>
       <installDirectory>/opt/ibm/wlp</installDirectory>
       <serverName>test</serverName>
    </configuration>
</plugin>

java-dump-server

---

Dump diagnostic information from the server JVM.

Additional Parameters

The following are the parameters supported by this goal in addition to the common server parameters and the common parameters.

Parameter	Description	Required
systemDump	Include system dump information. The default value is false.	No
heapDump	Include heap dump information. The default value is false.	No

Example:

<plugin>
    <groupId>net.wasdev.wlp.maven.plugins</groupId>
    <artifactId>liberty-maven-plugin</artifactId>
    <executions>
        ...
        <execution>
            <id>java-dump-server</id>
            <phase>post-integration-test</phase>
            <goals>
                <goal>java-dump-server</goal>
            </goals>
            <configuration>
                <heapDump>true</heapDump>
                <systemDump>true</systemDump>
            </configuration>
        </execution>
        ...
    </executions>
    <configuration>
       <installDirectory>/opt/ibm/wlp</installDirectory>
       <serverName>test</serverName>
    </configuration>
</plugin>

deploy

---

Deploy an application to a Liberty Profile server. The server instance must exist and must be running.

Additional Parameters

The following are the parameters supported by this goal in addition to the common parameters.

Parameter	Description	Required
appArtifact	Maven coordinates of an application to be deployed.	Yes, if appArchive is not set.
appArchive	Location of an application file to be deployed. The application type can be war, ear, rar, eba, zip, or jar.	Yes, if appArtifact is not set.
timeout	Maximum time to wait (in seconds) to verify that the deployment has completed successfully. The default value is 40 seconds.	No

Examples:

1. Single deploy of an application with the path of a file.

  <execution>
      <id>deploy-app</id>
      <phase>post-integration-test</phase>
      <goals>
          <goal>deploy</goal>
      </goals>
      <configuration>
          <appArchive>HelloWorld.war</appArchive>
      </configuration>
  </execution>

2. Single deploy of an application with maven coordinates.

  <execution>
      <id>deploy-by-appArtifact</id>
      <phase>post-integration-test</phase>
      <goals>
          <goal>deploy</goal>
      </goals>
      <configuration>
          <appArtifact>
              <groupId>com.mycompany.webapp</groupId>
              <artifactId>webapp</artifactId>
              <version>1.0</version>
              <type>war</type>
          </appArtifact>
      </configuration>
  </execution>

undeploy

---

Undeploy an application to a Liberty Profile server. The server instance must exist and must be running. If appArtifact or appArchive are not defined, the goal will undeploy all applications from the server.

Additional Parameters

The following are the parameters supported by this goal in addition to the common parameters.

Parameter	Description	Required
appArtifact	Maven coordinates of an application to be undeployed.	No
appArchive	Name of an application to be undeployed. The application type can be war, ear, rar, eba, zip, or jar.	No
patternSet	Includes and excludes patterns of applications to be undeployed.	No
timeout	Maximum time to wait (in seconds) to verify that the undeployment has completed successfully. The default value is 40 seconds.	No

Examples:

1. Single undeploy from an application file.

  <execution>
      <id>undeploy-by-appArchive</id>
      <phase>post-integration-test</phase>
      <goals>
          <goal>undeploy</goal>
      </goals>
      <configuration>
          <appArchive>HelloWorld.war</appArchive>
      </configuration>
  </execution>

2. Single undeploy from an application with maven coordinates.

 <execution>
     <id>undeploy-by-appArtifact</id>
     <phase>post-integration-test</phase>
     <goals>
         <goal>undeploy</goal>
     </goals>
     <configuration>
         <appArtifact>
             <groupId>com.mycompany.webapp</groupId>
             <artifactId>webapp</artifactId>
             <version>1.0</version>
             <type>war</type>
         </appArtifact>
     </configuration>
 </execution>

3. Undeploy all.

  <execution>
      <id>undeploy-by-appArtifact</id>
      <phase>post-integration-test</phase>
      <goals>
          <goal>undeploy</goal>
      </goals>
  </execution>

4. Undeploy from a patternSet.

  <execution>
      <id>undeploy-by-appArtifact</id>
      <phase>post-integration-test</phase>
      <goals>
          <goal>undeploy</goal>
      </goals>
      <configuration>
          <patternSet>
              <includes>*.war</includes>
              <excludes>webapp.war</excludes>
          </patternSet>
      </configuration>
  </execution>

install-feature

---

Install a feature packaged as a Subsystem Archive (esa) to the Liberty runtime.

To install the missing features declared in the server.xml file, don't specify any feature names in the features configuration (You still need to specify the acceptLicense parameter).

Additional Parameters

The following are the parameters supported by this goal in addition to the common parameters.

Parameter	Description	Required
feature	Specify the location of the Subsystem archive to be used. This can be an esa file, an IBM-Shortname or a Subsystem-SymbolicName of the Subsystem archive. The value can be a file name or a URL to the esa file.	No
acceptLicense	Automatically indicate acceptance of license terms and conditions.	No
to	Specify where to install the feature. The feature can be installed to any configured product extension location, or as a user feature (usr, extension). If this option is not specified the feature will be installed as a user feature.	No
from	Specifies a single directory-based repository as the source of the assets.	No

Examples:

1. Install specific features.

<plugin>
   <groupId>net.wasdev.wlp.maven.plugins</groupId>
   <artifactId>liberty-maven-plugin</artifactId>
   <executions>
       ...
       <execution>
           <id>install-feature</id>
           <phase>pre-integration-test</phase>
           <goals>
               <goal>install-feature</goal>
           </goals>
           <configuration>
               <features>
                   <acceptLicense>true</acceptLicense>
                   <feature>mongodb-2.0</feature>
                   <feature>ejbLite-3.2</feature>
               </features>
           </configuration>
       </execution>
       ...
   </executions>
   <configuration>
      <installDirectory>/opt/ibm/wlp</installDirectory>
      <serverName>test</serverName>
   </configuration>
</plugin>

2. Check the server.xml file and install the missing features.

<plugin>
   <groupId>net.wasdev.wlp.maven.plugins</groupId>
   <artifactId>liberty-maven-plugin</artifactId>
   <executions>
       ...
       <execution>
           <id>install-feature</id>
           <phase>pre-integration-test</phase>
           <goals>
               <goal>install-feature</goal>
           </goals>
           <configuration>
               <features>
                   <acceptLicense>true</acceptLicense>
               </features>
           </configuration>
       </execution>
       ...
   </executions>
   <configuration>
      <installDirectory>/opt/ibm/wlp</installDirectory>
      <serverName>test</serverName>
   </configuration>
</plugin>

uninstall-feature

---

Uninstall a feature from the Liberty runtime.

Additional Parameters

The following are the parameters supported by this goal in addition to the common parameters.

Parameter	Description	Required
feature	Specify the feature name to be uninstalled. This can be an IBM-Shortname or a Subsystem-SymbolicName of the Subsystem archive.	Yes

Example:

<plugin>
    <groupId>net.wasdev.wlp.maven.plugins</groupId>
    <artifactId>liberty-maven-plugin</artifactId>
    <executions>
        ...
        <execution>
            <id>install-feature</id>
            <phase>post-integration-test</phase>
            <goals>
                <goal>uninstall-feature</goal>
            </goals>
            <configuration>
                <features>
                    <feature>mongodb-2.0</feature>
                </features>
            </configuration>
        </execution>
        ...
    </executions>
    <configuration>
       <installDirectory>/opt/ibm/wlp</installDirectory>
       <serverName>test</serverName>
    </configuration>
</plugin>

install-apps

---

Copy applications specified as Maven compile dependencies to Liberty server's dropins or apps directory. Unlike the deploy goal, this goal only performs a simple copy operation. It does not require the server to be running and does not check if the application was successfully deployed.

Additional Parameters

The following are the parameters supported by this goal in addition to the common parameters.

Parameter	Description	Required
appsDirectory	The directory where the application files should be copied. The default value is dropins.	No
stripVersion	Strip artifact version when copying the application to Liberty runtime's application directory. The default value is false.	No

Example:

<project>
    ...
    <dependencies>
        <!-- SimpleServlet.war specified as a dependency -->
        <dependency>
            <groupId>wasdev</groupId>
            <artifactId>SimpleServlet</artifactId>
            <version>1.0</version>
            <type>war</type>
        </dependency>
    </dependencies>
    ...
    <build>
        <plugins>
            <plugin>
                <groupId>net.wasdev.wlp.maven.plugins</groupId>
                <artifactId>liberty-maven-plugin</artifactId>
                <executions>
                    ...
                    <execution>
                        <id>install-apps</id>
                        <phase>pre-integration-test</phase>
                        <goals>
                            <goal>install-apps</goal>
                        </goals>
                        <configuration>
                            <appsDirectory>apps</appsDirectory>
                            <stripVersion>true</stripVersion>
                        </configuration>
                    </execution>
                    ...
                </executions>
                <configuration>
                   <installDirectory>/opt/ibm/wlp</installDirectory>
                   <serverName>test</serverName>
                </configuration>
            </plugin>
        </plugins>
    </build>
    ...
</project>

Packaging types

liberty-assembly

The liberty-assembly Maven packaging type is used to create a packaged Liberty profile server Maven artifact out of existing server installation, compressed archive, or another server Maven artifact. Any applications specified as Maven compile dependencies will be automatically packaged with the assembled server. Liberty features can also be installed and packaged with the assembled server.

Example:

<project>
    ...
    <groupId>myGroup</groupId>
    <artifactId>myServer</artifactId>
    <!-- Create Liberty profile server assembly -->
    <packaging>liberty-assembly</packaging>
    ...
    <dependencies>
        <!-- Package SimpleServlet.war with server assembly -->
        <dependency>
            <groupId>wasdev</groupId>
            <artifactId>SimpleServlet</artifactId>
            <version>1.0</version>
            <type>war</type>
        </dependency>
    </dependencies>
    ...
    <build>
        <plugins>
            <!-- Enable liberty-maven-plugin -->
            <plugin>
                <groupId>net.wasdev.wlp.maven.plugins</groupId>
                <artifactId>liberty-maven-plugin</artifactId>
                <version>1.1</version>
                <extensions>true</extensions>
                <configuration>
                    <installDirectory>/opt/ibm/wlp</installDirectory>
                    <serverName>test</serverName>
                    <features>
                        <acceptLicense>true</acceptLicense>
                        <feature>mongodb-2.0</feature>
                    </features>
                </configuration>
            </plugin>
        </plugins>
    </build>
    ...
</project>

Archetypes

liberty-plugin-archetype

liberty-plugin-archetype is used to generate a basic multi-module project that builds a simple web application, deploys and tests it on the Liberty profile server. It also creates a Liberty profile server package that includes the application.

Usage

mvn archetype:generate \
    -DarchetypeGroupId=net.wasdev.wlp.maven \
    -DarchetypeArtifactId=liberty-plugin-archetype \
    -DgroupId=test \
    -DartifactId=test \
    -Dversion=1.0-SNAPSHOT