11.16. Maven automated deployment

11.16.1. Problem description ¶

In general, multiple teams are involved in the development process mentioned above. One team may be responsible for submitting code, another team for building, and so on. It is likely that any step can go wrong due to the human operations and multi-team environments involved. For example, the older version was not updated on the network machine, and then the deployment team redeployed the earlier build.

11.16.2. Solution ¶

Automate deployment by combining the following scenarios:

• Build and publish projects using Maven

• Use SubVersion, source code repository to manage source code

• Use remote warehouse management software (Jfrog or Nexus) to manage project binaries.

11.16.3. Modify the pom.xml of the project ¶

We will use plug-ins released by Maven to create an automated release process.

For example, the pom.xml file code for the bus-core-api project is as follows:

<projectxmlns="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><groupId>bus-core-api</groupId><artifactId>bus-core-api</artifactId><version>1.0-SNAPSHOT</version><packaging>jar</packaging><scm><url>http://www.svn.com</url><connection>scm:svn:http://localhost:8080/svn/jrepo/trunk/
Framework</connection><developerConnection>scm:svn:${username}/${password}@localhost:8080:
common_core_api:1101:code</developerConnection></scm><distributionManagement><repository><id>Core-API-Java-Release</id><name>Release
repository</name><url>http://localhost:8081/nexus/content/repositories/
Core-Api-Release</url></repository></distributionManagement><build><plugins><plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-release-plugin</artifactId><version>2.0-beta-9</version><configuration><useReleaseProfile>false</useReleaseProfile><goals>deploy</goals><scmCommentPrefix>[bus-core-api-release-checkin]-</scmCommentPrefix></configuration></plugin></plugins></build></project>

Some of the important element nodes that we often use in the pom.xml file are shown in the following table:

11.16.4. Maven Release plug-in ¶

Maven uses the maven-release-plugin plug-in to accomplish the following tasks.

mvn release:clean

Clean up the workspace to ensure the success of the latest release process.

mvn release:rollback

If the last release process is unsuccessful, rolling back the modified workspace code and configuration ensures that the release process is successful.

mvn release:prepare

Perform a variety of actions:

• Check to see if there are any local changes that have not yet been committed

• Make sure there are no dependencies for snapshots

• Change the version information of the application for release

• Update the POM file to SVN

• Run the test case

• Submit the modified POM file

• Mark the code on SVN

• Increase the version number and attach snapshots for future release

• Submit the modified POM file to SVN

mvn release:perform

Switch the code to where it was previously marked and run the Maven deployment target to deploy the WAR file or build the corresponding structure into the repository.

Open the command terminal, go to the C:> MVN > bus-core-api directory, and execute the following mvn command.

C:\MVN\bus-core-api>mvn release:prepare

Maven began to build the entire project. After the build is successful, you can run the following mvn command.

C:\MVN\bus-core-api>mvn release:perform

After the build is successful, you can verify that the JAR file uploaded under your repository is valid.