Sign In Start Free Trial

Book Overview & Buying
Table Of Contents
Feedback & Rating

Mastering Apache Maven 3

By : Siriwardena

4.3 (3)

Mastering Apache Maven 3

4.3 (3)

By: Siriwardena

Overview of this book

If you are working with Java or Java EE projects and you want to take full advantage of Maven in designing, executing, and maintaining your build system for optimal developer productivity, then this book is ideal for you. You should be well versed with Maven and its basic functionality if you wish to get the most out of the book.

Preface

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Free Chapter

1. Apache Maven Quick Start

1. Apache Maven Quick Start

A quick introduction

Installing Apache Maven

Configuring the heap size

Monitoring the build

Remote debugging

Convention over configuration

IDE integration

Troubleshooting

Summary

2. Demystifying Project Object Model

2. Demystifying Project Object Model

Project Object Model

The POM hierarchy

Super POM

POM extending and overriding

Maven coordinates

Parent POM file

Managing POM dependencies

Summary

3. Maven Configuration

3. Maven Configuration

Maven Wagon

Proxy authentication

Secured repositories

Encrypting credentials in settings.xml

Source Control Management systems

Local repository location

Mirrored repositories

Deploying artifacts

Enabling Maven logging

Summary

4. Build Lifecycles

4. Build Lifecycles

Standard lifecycles in Maven

Lifecycle bindings

Building a custom lifecycle

Lifecycle extensions

Summary

5. Maven Plugins

5. Maven Plugins

Common Maven plugins

Plugin discovery and execution

Plexus

Maven and Dependency Injection

Developing custom plugins

Summary

6. Maven Assemblies

6. Maven Assemblies

The assembly plugin

The assembly descriptor

Artifact/resource filtering

Assembly help

A runnable, standalone Maven project

Summary

7. Maven Archetypes

7. Maven Archetypes

Archetype quickstart

The batch mode

Archetype catalogues

The archetype plugin goals

Maven plugins with the archetype plugin

Java EE web applications with the archetype plugin

Android mobile applications with the archetype plugin

EJB archives with the archetype plugin

JIRA plugins with the archetype plugin

Spring MVC applications with the archetype plugin

Building a custom archetype

Summary

8. Maven Repository Management

8. Maven Repository Management

Maven repositories

The update policy

Multiple repositories

The Maven repository manager

Creating a proxy repository

Creating a virtual repository

Blocking selected artifacts

Inclusive and exclusive routing

Scheduled tasks

Artifact indexing

Nexus plugins

A repository metadata model

Summary

9. Best Practices

9. Best Practices

Dependency management

Defining a parent module

POM properties

Avoiding repetitive groupId and version tags and inherit from the parent POM

Following naming conventions

Maven profiles

Think twice before you write your own plugin

The Maven release plugin

The Maven enforcer plugin

Avoid using un-versioned plugins

Using exclusive and inclusive routes

Avoid having both release and snapshot repositories in the same group repository

Avoid having both proxy and hosted repositories in the same group repository

Minimizing the number of repositories

Using mirrorOf instead of changing repository URLs

Descriptive parent POM files

Documentation is your friend

Avoid overriding the default directory structure

Using SNAPSHOT versioning during development

Get rid of unused dependencies

Avoid keeping credentials in application POM files

Avoid using deprecated references

Avoid repetition – use archetypes

Avoid using maven.test.skip

Share resources – avoid duplicates

Summary

Index

Index

Customer Reviews

4.3 (3)

5 star

33.3%

4 star

66.7%

3 star

0

2 star

0

1 star

0

Monitoring the build

The most popular way of starting a Maven build is by using the mvn clean install command. This will build all the Maven modules under your project and install the artifacts to your local repository. For a simple project, the entire build process will take less than a minute. However, for a large project, to create an online build with a clean repository could even take more than 3 hours: this is not an exaggeration. If you look at the WSO2 Carbon complete code base, the complete build process takes more than four hours to run with all the test cases. During a long-running build process, it is extremely important that we monitor the build properly.

Note

WSO2 Carbon is a framework that is written on top of OSGi to build servers. All WSO2 products, which are 100 percent open source and released under Apache 2.0 license, are built on top of WSO2 Carbon. WSO2 Carbon code base is available at https://svn.wso2.org/repos/wso2/carbon/.

The following screenshot shows an overview of the JVisualVM tool running a Maven build:

Monitoring the build

Note

JVisualVM is a Java virtual machine monitoring, troubleshooting, and profiling tool. To learn more about it, refer http://docs.oracle.com/javase/6/docs/technotes/tools/share/jvisualvm.html.

The JVisualVM tool that comes with the JDK distribution can be used to monitor a running Maven build. First, we need to start the Maven build and then start JVisualVM using the following command:

$ jvisualvm

This command will start the JVisualVM tool. Once the tool gets started, select org.codehaus.plexus.classworlds.launcher.Launcher from the Applications tab to monitor the running Maven build. You can gather many important statistics using JVisualVM, and based on that you can optimize your system resources for an optimal Maven build.

The following screenshot shows JVisualVM statistics of a running Maven build:

Monitoring the build

Search

Your notes and bookmarks