To allow for repeatable, faster builds in a continuous build environment, it’s often a good idea to use a central repository to cache common assets and prevent the need to download assets from the internet for each build. Using Nexus allows for those transfers to occur over your local network for previously downloaded assets.
You can download the WAR from:
And install on your Java application server, such as Apache Tomcat, via normal means.
If you are using Maven, you’ll need to make appropriate changes in (
/.m2/settings.xml) to direct your builds to use Nexus.
Jenkins and other build automation tools will require similar changes.
I’ve migrated most of my projects to Maven, but occasionally have some developers that prefer to use Ant in their development environments. One problem that I used to have with Ant was that it required all dependencies to be checked into the SCM repository for each project. I recently found an Ant plugin that allows for it to read the Maven pom.xml and download the required dependencies, thus making projects MUCH easier to maintain! the steps are very simple.
Maven – pom.xml
- Make sure that you have your dependencies (nexus?) setup and tested here.
Maven – global settings.xml
- Make sure that your repositories are correctly configured.
Ant – build.xml (very minimal, I usually add as a step in existing scripts vs. using as standalone)
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<project name="example" basedir="." default="dependencies" xmlns:artifact="antlib:org.apache.maven.artifact.ant">
<taskdef uri="antlib:org.apache.maven.artifact.ant" classpath="ant/maven-ant-tasks-2.1.3.jar" />
<echo message="--- getting dependencies from maven pom.xml ---" />
<artifact:pom id="pom" file="pom.xml" /><!-- settingsFile="settings.xml" -->
<artifact:dependencies filesetId="test.dependencies" pomRefId="pom" useScope="test" />
<fileset refid="test.dependencies" />
<mapper type="flatten" />
- Make sure that you put the JAR (
maven-ant-tasks-2.1.3.jar) in the proper place…
If everything is working well, you can now purge most of the JAR’s that reside inside your web projects as the Ant build process can retrieve them based on values in the Maven pom.xml file.