Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Advanced Search Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Maven Essentials
  • Table Of Contents Toc
  • Feedback & Rating feedback
Maven Essentials

Maven Essentials

By : Russell E Gold, Siriwardena
3.9 (8)
close
close
Maven Essentials

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.
Table of Contents (9 chapters)
close
close
close
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
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
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
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
4. Maven Plugins
4. Maven Plugins
Common Maven plugins
Plugin discovery and execution
Summary
5
5. Build Lifecycles
5. Build Lifecycles
Standard lifecycles in Maven
Lifecycle bindings
Lifecycle extensions
Summary
6
6. Maven Assemblies
6. Maven Assemblies
The assembly plugin
The assembly descriptor
Artifact/resource filtering
Assembly help
A runnable standalone Maven project
Summary
7
7. Best Practices
chevron up
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
8
Index
Index

Avoiding repetition – use archetypes

When we create a Java project, we need to structure it in different ways based on the type of the project. If it's a Java EE web application then we need to have a WEB-INF directory and a web.xml file. If it's a Maven plugin project, we need to have a Mojo class, which extends from org.apache.maven.plugin.AbstractMojo. Since each type of project has its own predefined structure, why would everyone have to build the same structure again and again? Why don't we start with a template? Each project can have its own template and the developers can extend the template to suit their requirements. Maven archetypes address this concern. Each archetype is a project template.

We discussed Maven archetypes in detail, in Chapter 3, Maven Archetypes.

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
Start a 7-day FREE trial
End of Section 18
Next Section
bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete