Book Image

Maven Essentials

By : Russell E Gold, Prabath Siriwardena
5 (1)
Book Image

Maven Essentials

5 (1)
By: Russell E Gold, Prabath 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.
Table of Contents (15 chapters)
Maven Essentials
Credits
About the Author
Acknowledgments
About the Reviewer
www.PacktPub.com
Preface
Index

Common Maven plugins


Maven plugins are mostly developed under the Apache Maven project itself, as well as under the Codehaus and Google Code projects. The following sections list out a set of commonly used Maven plugins and their usages.

The clean plugin

As discussed earlier, the clean plugin executes the clean goal of the Maven clean plugin to remove any of the working directories and other resources created during the build, as follows:

$ mvn clean:clean

The Maven clean plugin is also associated with the clean lifecycle. If you just execute mvn clean, the clean goal of the clean plugin will get executed.

You do not need to explicitly define the Maven clean plugin in your project POM file. Your project inherits it from the Maven super POM file. In Chapter 2, Understanding the Project Object Model (POM), we discussed the Maven super POM file in detail. The following configuration in the super POM file associates the Maven clean plugin with all the Maven projects:

<plugin>
  <artifactId...