Mastering Apache Maven 3

Book Image

Mastering Apache Maven 3

Book Image

Mastering Apache Maven 3

Overview of this book

Credits

About the Author

About the Author

Acknowledgments

Acknowledgments

About the Reviewers

About the Reviewers

www.PacktPub.com

www.PacktPub.com

Preface

Free Chapter

Apache Maven Quick Start

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

Demystifying Project Object Model

Demystifying Project Object Model

Project Object Model

The POM hierarchy

POM extending and overriding

Maven coordinates

Parent POM file

Managing POM dependencies

Maven Configuration

Maven Configuration

Proxy authentication

Secured repositories

Encrypting credentials in settings.xml

Source Control Management systems

Local repository location

Mirrored repositories

Deploying artifacts

Enabling Maven logging

Build Lifecycles

Build Lifecycles

Standard lifecycles in Maven

Lifecycle bindings

Building a custom lifecycle

Lifecycle extensions

Maven Plugins

Common Maven plugins

Plugin discovery and execution

Maven and Dependency Injection

Developing custom plugins

Maven Assemblies

Maven Assemblies

The assembly plugin

The assembly descriptor

Artifact/resource filtering 

A runnable, standalone Maven project

Maven Archetypes

Maven Archetypes

Archetype quickstart

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

Maven Repository Management

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

A repository metadata model

Best Practices

Dependency management

Defining a parent module

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

Following naming conventions

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

Index

Customer Reviews

5 star

0

4 star

0

3 star

0

2 star

0

1 star

0

The archetype plugin goals

So far in this chapter, we have only discussed the generate and crawl goals of the archetype plugin. The following goals are associated with the archetype plugin:

archetype:generate: The generate goal creates a Maven project corresponding to the selected archetype. This accepts the archetypeGroupId, archetypeArtifactId, archetypeVersion, filter, interactiveMode, archetypeCatalog, and baseDir arguments. We have already discussed almost all of these arguments in detail.
archetype:update-local-catalog: The update-local-catalog goal has to be executed against a Maven archetype project. This will update the local archetype catalogue with the new archetype. The local archetype catalogue is available at ~/.m2/archetype-catalog.xml. We'll use the update-local-catalog goal later in this chapter when we create our own Maven archetype.
archetype:jar: The jar goal has to be executed against a Maven archetype project, and it will create a JAR file out of it. This accepts the archetypeDirectory...