Chandra Guntur

Many of us have been used to JUnit 4 as a formidable unit testing framework, here is an introduction to JUnit 5, with references to JUnit 4.

Maven uses the version as a coordinate in identifying an artifact, which are covered in “Understanding Apache Maven (Part 9)”.

Maven is a plugin-execution framework: plugins are an assembly of goals, code written as MOJOs (Maven’s plain Old Java Objects).

Maven can depend on constraints external to what is packaged. Examples include the JDK to use (assuming there are several JDKs on the device).

Not meant as a full dissection of the Apache Maven pom.xml, this article will go through some of its common portions.

In this, part 5 of the series, a walkthrough of the topic of Maven dependencies is covered!

Apache Maven executions are tied to lifecycles. A lifecycle groups a sequence of activities.

Maven provides three basic lifecycles for its standard build management. More lifecycles can be created as needed, though that is a rare need. There are three standard lifecycles provided by Maven.

In Part 3 of the series, an explanation of dependency coordinates and “distinguishers” as well as a more detailed look at POM hierarchies are covered.

First, a maven POM is not a popular pomegranate juice nor is it related to the colorful pom-poms.

A Maven POM is definitely is wonderful and brings as much joy to a developer as does a pom-pom to a kid.