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 Mastering Apache Maven 3
  • Table Of Contents Toc
  • Feedback & Rating feedback
Mastering Apache Maven 3

Mastering Apache Maven 3

By : Siriwardena
4.3 (3)
close
close
Mastering Apache Maven 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.
Table of Contents (11 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
A quick introduction
Installing Apache Maven
Configuring the heap size
Monitoring the build
Remote debugging
Convention over configuration
IDE integration
Troubleshooting
Summary
2
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
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
4. Build Lifecycles
4. Build Lifecycles
Standard lifecycles in Maven
Lifecycle bindings
Building a custom lifecycle
Lifecycle extensions
Summary
5
5. Maven Plugins
5. Maven Plugins
Common Maven plugins
Plugin discovery and execution
Plexus
Maven and Dependency Injection
Developing custom plugins
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. 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
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
9. Best Practices
chevron up
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
10
Index
Index

Avoid using un-versioned plugins

If you have associated a plugin with your application POM, without a version, then Maven will download the corresponding maven-metadata.xml file and store it locally. Only the latest released version of the plugin will be downloaded and used in the project. This can easily create certain uncertainties. Your project might work fine with the current version of a plugin, but later if there is a new release of the same plugin, your Maven project will start to use the latest one automatically. This can result in unpredictable behaviors and lead to a debugging mess.

It is always recommended that you specify the plugin version along with the plugin configuration. You can enforce this as a rule, with the Maven enforcer plugin, as shown in the following code:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-enforcer-plugin</artifactId>
  <version>1.3.1</version>
  <executions>
    <execution...

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 9
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