Sign In Start Free Trial

Book Overview & Buying
Table Of Contents
Feedback & Rating

Maven Essentials

By : Russell E Gold, Siriwardena

3.9 (8)

Maven Essentials

3.9 (8)

By: Russell E Gold, Siriwardena

Overview of this book

Maven is the #1 build tool used by developers and it has been around for more than a decade. Maven stands out among other build tools due to its extremely extensible architecture, which is built on of the concept of convention over configuration. It’s widely used by many open source Java projects under Apache Software Foundation, Sourceforge, Google Code, and more. Maven Essentials is a fast-paced guide to show you the key concepts in Maven and build automation. We get started by introducing you to Maven and exploring its core concepts and architecture. Next, you will learn about and write a Project Object Model (POM) while creating your own Maven project. You will also find out how to create custom archetypes and plugins to establish the most common goals in build automation. After this, you’ll get to know how to design the build to prevent any maintenance nightmares, with proper dependency management. We then explore Maven build lifecycles and Maven assemblies. Finally, you will discover how to apply the best practices when designing a build system to improve developer productivity.

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

Installing Apache Maven

Configuring the heap size

Hello Maven!

Convention over configuration

Maven repositories

IDE integration

Troubleshooting

Summary

2. Understanding the Project Object Model (POM)

2. Understanding the Project Object Model (POM)

Project Object Model (POM)

POM hierarchy

Super POM

POM extending and overriding

Maven coordinates

The parent POM

Managing POM dependencies

Summary

3. Maven Archetypes

3. Maven Archetypes

Archetype quickstart

Batch mode

Archetype catalogues

The archetype plugin goals

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

Summary

4. Maven Plugins

4. Maven Plugins

Common Maven plugins

Plugin discovery and execution

Summary

5. Build Lifecycles

5. Build Lifecycles

Standard lifecycles in Maven

Lifecycle bindings

Lifecycle extensions

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. Best Practices

7. Best Practices

Dependency management

Defining a parent module

POM properties

Avoiding repetitive groupIds and versions, and inheriting from the parent POM

Following naming conventions

Think twice before you write your own plugin. You may not need it!

The Maven release plugin

The Maven enforcer plugin

Avoiding the use of unversioned plugins

Descriptive parent POM files

Documentation is your friend

Avoid overriding the default directory structure

Using SNAPSHOT versioning during the development

Get rid of unused dependencies

Avoiding keeping credentials in application POM files

Avoiding using deprecated references

Avoiding repetition – use archetypes

Avoiding using maven.test.skip

Summary

Index

Index

Customer Reviews

3.9 (8)

5 star

37.5%

4 star

25%

3 star

25%

2 star

12.5%

1 star

0

Artifact/resource filtering

We had a filters configuration, defined for the assembly plugin in the first example with the WSO2 Identity Server. This instructs the assembly plugin to apply the filter criteria defined in the provided filter or the set of filters for the files that are being copied to the final archive file. If you want to apply a filter to a given file, then you should set the value of the filtered element to true.

The following configuration shows how to define a filter:

<filters>
  <filter>${basedir}/src/assembly/filter.properties</filter>
</filters>

Let's take a look at the file ${basedir}/src/assembly/filter.properties. This file defines a set of name/value pairs. The name is a special placeholder, which should be enclosed between ${ and } in the file to be filtered, and it will be replaced by the value during the filtering process:

product.name=WSO2 Identity Server 
product.key=IS 
product.version=5.0.0 
hotdeployment=true 
hotupdate=true 
default...

Search

Your notes and bookmarks