WASdev/ci.maven

Name: ci.maven

Owner: WASdev

Description: Maven plugins for managing Liberty profile servers #devops

Created: 2013-07-03 15:30:54.0

Updated: 2018-01-04 17:39:36.0

Pushed: 2017-12-21 19:27:53.0

Homepage:

Size: 907

Language: Java

GitHub Committers

User	Most Recent Commit	# Commits

Other Committers

User	Email	Most Recent Commit	# Commits

README

ci.maven

Collection of Maven plug-ins and archetypes for managing WebSphere Application Server Liberty servers and applications.

• Build
• Plug-ins
  • liberty-maven-plugin
    • Configuration
    • Goals
• Packaging types
• liberty-assembly
• Archetypes
  • liberty-plugin-archetype
  • liberty-archetype-mp
  • liberty-archetype-webapp
  • liberty-archetype-ear

Build

Use Maven 3.x to build the Liberty plug-ins and archetypes.

• mvn install : builds the plug-in and the archetypes.
• mvn install -Poffline-its -DwlpInstallDir=<liberty_install_directory> : builds the plug-in and the archetypes and runs the integration tests by providing an existing installation.
• mvn install -Ponline-its -DwlpVersion=<liberty_version> -DwlpLicense=<liberty_license_code> : builds the plug-in and archetypes 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.

Information for release 2.0

A number of new features and changes were made in release 2.0 of the Liberty Maven plug-in and are described here.

Plug-ins

liberty-maven-plugin

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

Configuration

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

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

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

ject>
...
<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>
...
oject>

Liberty installation configuration

liberty-maven-plugin must first be configured with the Liberty server 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 a Liberty server from the Liberty repository or other location using the install parameter. By default, the plug-in installs the Liberty runtime with the Java EE 7 Web Profile features from the Liberty repository.

Goals

The liberty-maven-plugin provides the following goals.

| Goal | Description | | ——— | ———— | | install-server | Installs the Liberty runtime. This goal is implicitly invoked by all the other plug-in goals and usually does not need to be executed explicitly. | | create-server | Create a Liberty server. | | start-server | Start a Liberty server in background. The server instance will be automatically created if it does not exist. | | test-start-server | Allows you to bypass automatically starting the server during the pre-integration-test phase with pom configuration or a Liberty-specific command line argument. | | run-server | Start a Liberty server in foreground. The server instance will be automatically created if it does not exist. | | stop-server | Stop a Liberty server. The server instance must exist and must be running. | | test-stop-server | Allows you to bypass automatically stopping the server during the post-integration-test phase with pom configuration or a Liberty-specific command line argument. | | package-server | Package a Liberty server. | | clean-server | Deletes every file in the ${outputDirectory}/logs, ${outputDirectory}/workarea, ${userDirectory}/dropins or ${userDirectory}/apps. | | dump-server | Dump diagnostic information from the server into an archive. | | java-dump-server | Dump diagnostic information from the server JVM. | | deploy | Deploy an application to a Liberty server. The server instance must exist and must be running. | | undeploy | Undeploy an application to a Liberty server. The server instance must exist and must be running. | | install-feature | Install a feature packaged as a Subsystem Archive (esa) to the Liberty runtime. | | uninstall-feature | Uninstall a feature from the Liberty runtime. | | install-apps | Copy applications specified as Maven compile dependencies to Liberty server's dropins or apps directory. | | compile-jsp | Compile JSPs in the src/main/webapp into the target/classes directory | | display-url | Display the application URL in the default browser. |

Common Parameters

Parameters shared by all goals. See common parameters.

Common Server Parameters

Additional parameters shared by all server-based goals. See common server parameters.

Extensions

Extensions are goals that improve the compatibility or user experience of third party libraries used with Liberty. The liberty-maven-plugin provides the following extensions.

| Extension | Description | | ——— | ———— | | configure-arquillian | Integrates arquillian.xml configuration for the Liberty Managed and Remote Arquillian containers in the liberty-maven-plugin. Automatically configures required arquillian.xml parameters for the Liberty Managed container. |

Packaging types

liberty-assembly

The liberty-assembly Maven packaging type is used to create a packaged Liberty 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. Any application or test code included in the project is automatically compiled and tests run at appropriate unit or integration test phase. Application code is installed as a loose application WAR file if installAppPackages is set to all or project and looseApplication is set to true.

The liberty-assembly default lifecycle includes:

| Phase | Goal | | —– | —- | | pre-clean | liberty:stop-server | | process-resources | maven-resources-plugin:resources | | compile | maven-compiler-plugin:compile | | process-test-resources | maven-resources-plugin:testResources | | test-compile | maven-compiler-plugin:testCompile | | test | maven-surefire-plugin:test | | prepare-package | liberty:create-server, liberty:install-feature | | package | liberty:install-apps, liberty:package-server | | pre-integration-test | liberty:test-start-server | | integration-test | maven-failsafe-plugin:integration-test | | post-integration-test | liberty:test-stop-server | | verify | maven-failsafe-plugin:verify | | install | maven-install-plugin:install | | deploy | maven-deploy-plugin:deploy |

Example:

ject>
...
<groupId>myGroup</groupId>
<artifactId>myServer</artifactId>
<!-- Create Liberty 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>2.0</version>
            <extensions>true</extensions>
            <configuration>
                <installDirectory>/opt/ibm/wlp</installDirectory>
                <serverName>test</serverName>
                <features>
                    <acceptLicense>true</acceptLicense>
                    <feature>mongodb-2.0</feature>
                </features>
                <looseApplication>true</looseApplication>
                <installAppPackages>all</installAppPackages>
            </configuration>
        </plugin>
    </plugins>
</build>
...
oject>

Archetypes

liberty-plugin-archetype

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

Usage

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

liberty-archetype-mp

liberty-archetype-mp is used to generate a basic single-module project that builds a simple MicroProfile application then deploys and tests on a Liberty server. It also creates a minified, runnable Liberty server package that includes the application. The generated project includes liberty-maven-app-parent parent pom that binds liberty-maven-plugin goals to the Maven default build lifecycle.

Usage

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

By default, the runtime used is the WebSphere Liberty MicroProfile package. To change to use Open Liberty, you can set -DlibertyGroupId=io.openliberty and -DlibertyArtifactId=openliberty-runtime. For example:

mvn archetype:generate \
    -DarchetypeGroupId=net.wasdev.wlp.maven \
    -DarchetypeArtifactId=liberty-archetype-mp \
    -DarchetypeVersion=2.1.3 \
    -DgroupId=test \
    -DartifactId=test \
    -DlibertyGroupId=io.openliberty \
    -DlibertyArtifactId=openliberty-runtime \
    -Dversion=1.0-SNAPSHOT

By default, the liberty-maven-plugin version is set the same as the liberty-archetype-mp archetype version used. To specify a different version of the plugin, use the wlpPluginVersion parameter. For example, you could set -DwlpPluginVersion=2.1.

liberty-archetype-webapp

liberty-archetype-webapp is used to generate a basic single-module project that builds a simple web application then deploys and tests on a Liberty server. It also creates a minified, runnable Liberty server package that includes the application. The generated project includes liberty-maven-app-parent parent pom that binds liberty-maven-plugin goals to the Maven default build lifecycle.

Usage

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

By default, the liberty-maven-plugin version is set the same as the liberty-archetype-webapp archetype version used. To specify a different version of the plugin, use the wlpPluginVersion parameter. For example, you could set -DwlpPluginVersion=2.1.

liberty-archetype-ear

liberty-archetype-ear is used to generate a multi-module project that includes an EJB module, a web application module and an EAR module. In the EAR module, it packages the application in a Java EE 7 Enterprise Archive then deploys and tests on a Liberty server. It also creates a minified, runnable Liberty server package that includes the application EAR file. The generated project includes liberty-maven-app-parent parent pom that binds liberty-maven-plugin goals to the Maven default build lifecycle.

Usage

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

By default, the liberty-maven-plugin version is set the same as the liberty-archetype-ear archetype version used. To specify a different version of the plugin, use the wlpPluginVersion parameter. For example, you could set -DwlpPluginVersion=2.1.

If you are using a snapshot version of liberty-archetype-webapp or liberty-archetype-ear, then you will also need to add the following archetype repository to ${user.home}/.m2/settings.xml:

tings>
...
<profiles>
    <profile>
        <id>archetype-snapshot-repo</id>
        <properties>
            <archetypeRepository>https://oss.sonatype.org/content/repositories/snapshots
            </archetypeRepository>
        </properties>
        <repositories>
            <repository>
                <id>sonatype-nexus-snapshots</id>
                <name>Sonatype Nexus Snapshots</name>
                <url>https://oss.sonatype.org/content/repositories/snapshots/
                </url>
                <releases>
                    <enabled>false</enabled>
                </releases>
                <snapshots>
                    <enabled>true</enabled>
                </snapshots>
            </repository>
        </repositories>
        <pluginRepositories>
            <pluginRepository>
                <id>sonatype-nexus-snapshots</id>
                <name>Sonatype Nexus Snapshots</name>
                <url>https://oss.sonatype.org/content/repositories/snapshots/
                </url>
                <releases>
                    <enabled>false</enabled>
                </releases>
                <snapshots>
                    <enabled>true</enabled>
                </snapshots>
            </pluginRepository>
        </pluginRepositories>
    </profile>
</profiles>
<activeProfiles>
    <activeProfile>archetype-snapshot-repo</activeProfile>
</activeProfiles>
ttings>