IN28MINUTES

Java Tools and Frameworks - Introduction To Maven

Sep 4, 2019
3 minute read

In this article, we get a brief introduction to Maven, and see how it helps in managing project dependencies.

You will learn

  • What is Maven?
  • Why do we need Maven in the Java World?
  • How does Maven do dependency management?
  • How does Maven help you to build and deploy projects?

Java Programmer Essentials

As we go towards microservices architectures, what should a Java Programmer learn?

This is the fourth article in series of six articles on Java Programmer Essentials :

What Is Maven?

When we develop a Java software project, such as a microservice, the major dependencies we need are:

  • Spring MVC framework.
  • Spring framework
  • Hibernate

In addition to these 3 direct dependencies, we need to include their individual dependencies as well. So we need the dependencies of Spring MVC, Spring and Hibernate.

Let’s consider an example: REST API typically returns JSON responses. Spring MVC needs to convert Java Bean to JSON. It makes use of the Jackson framework to do the conversion. Jackson framework is a dependency of Spring MVC.

What if I manually download all the jars?

It is quite a task at project start-up, because you need to download a large number of JARs in the proper way, and set them up in the project folder.

The flip side of doing this manually is that each time there is a change in version of a dependency, you need to manually download the new version of dependency and its dependencies again.

Enter Maven

Maven provides dependency management. Any Maven project contains a file called pom.xml. In this file, we specify the dependencies that we need. This is done within the tag.

Example pom.xml

Within each tag, we specify the dependency we need for an application to work. Maven reads this pom.xml file, downloads the dependencies and transitive dependencies (dependencies of dependencies) , and makes them available for your project.

image info

Dependency Management With Maven

Identifying Artifacts

In order to describe each of the artifacts stored here, Maven uses two tags - and . In addition to that, there is also a version that is maintained for each artifact. using these 3 identifiers, Maven can retrieve the correct version of the required dependency.

Managing Transitive Dependencies

When Maven downloads a particular artifact, it also downloads those dependencies of this artifact that are needed in the project. These are known as transitive dependencies. This reduces the amount of effort that is spent on enumerating all the artifacts.

Maven Does A Lot More!

The truth is in the Java world, Maven does a lot more than just dependency management.

Building Deployable unit - Jars and Wars

Suppose we want to deploy an application to a different environment. We do not want to take the source code and build it again!

We can create an application deployable unit JAR/WAR/EAR and use it in other environments. Maven enables us to create application deployable unit in a simple way.

This entire sequence is called a build process, thereby making Maven a build tool as well.

Summary

In this article, we had an introduction on Maven. Maven is primarily used as a dependency management tool. In a large Java project, managing application dependencies manually is a daunting task. Maven steps up by automating the dependency identification and download process. Maven is also used in the Java world as an efficient build tool.

Do check out our video on the same topic:

image info

10 Step Reference Courses

Image Image Image Image Image

in28Minutes is helping 300,000 Learners across the world reach their learning goals. Click here for the complete catalogue of 30 Courses.

Related Posts

Spring Boot Tutorials for Beginners

At in28Minutes, we are creating a number of tutorials with videos, articles & courses on Spring Boot for Beginners and Experienced Developers. This resources will help you learn and gain expertise at Spring Boot.

Spring and Spring Boot Video Tutorials for Beginners

At in28Minutes, we are creating a number of tutorials with videos, articles & courses on Spring Boot for Beginners and Experienced Developers. Here's a list of video tutorials and courses for you

Software Design - Separation Of Concerns - with examples

Software architects and programmers love having Seperation of Concerns. What is it? Why is it important? Let's get started.

Object Oriented Software Design - Solid Principles - with examples

Software design is typically complex. Object oriented design takes it to the next level. There are a number of design patterns and other stuff to be aware of. Can we make things simple? What are the goals to aim for when you are doing object oriented design? SOLID Principles is a great starting point for Object Oriented Design.

Software Design - Open Closed Principle - with examples

Open Closed Principle is one of the SOLID Principles. You want your code to be easily extended. How do you achieve it with minimum fuss? Let's get started.

Software Design - What is Dependency Inversion Principle?

Dependency Inversion Principle is one of the important SOLID Principles. Dependency Inversion Principle is implemented by one of the most popular Java frameworks - Spring. What is it all about? How does it help you design good applications?

Introduction to Four Principles Of Simple Design

With agile and extreme programming, the focus is on keeping your design simple. How do you keep your design simple? How do you decide whether your code is good enough?

Software Design - Single Responsibility Principle - with examples

For me, Single Responsibility Principle is the most important design principle. What is Single Responsibility Principle? How do you use it? How does it help with making your software better? Let's get started.

REST API Best Practices - With Design Examples from Java and Spring Web Services

Designing Great REST API is important to have great microservices. How do you design your REST API? What are the best practices?

Designing REST API - What is Code First Approach?

Designing Great REST API is important to have great microservices. Code First approach focuses on generating the contract from code. Is it the best possible approach?