Home
PreviousNext
1. Introduction1.1. Course Structure1.2. Learning Goals1.3. Course Lecturers1.4. Topics1.5. Bibliography1.6. Tools1.7. Evaluation1.8. Agreements
2. Course Project2.1. Scope2.2. Rules of the Game2.3. Important Dates2.4. Requirements2.5. Tips
3. Git 1013.1. Introduction3.2. Installing Git3.3. Basic shell commands3.4. Git commands3.5. Ignoring files3.6. Branches3.7. Remote repositories
4. How Java Works4.1. Introduction4.2. Java Architecture4.3. Variables and Parameters4.4. Java Memory Model
5. Exception Handling5.1. Introduction5.2. Exception Types5.3. Declaring Exceptions Thrown by Methods5.4. Throwing Exceptions5.5. Custom Exceptions5.6. Accessing the Stack Trace
6. Inheritance6.1. Introduction6.2. Interfaces6.3. Method Overriding6.4. Multiple Inheritance6.5. Abstract Classes6.6. Method Overloading6.7. Polymorphism6.8. The Object Class6.9. Casting
7. Generic Programming7.1. Introduction7.2. Generic Methods7.3. Bounded and Unbounded Type Parameters7.4. Generic Types
8. Arrays8.1. One Dimensional Arrays8.2. Multidimensional Arrays8.3. The Arrays class8.4. Varags8.5. Limitations
9. Java Collections Framework9.1. Introduction9.2. The Collection Interface9.3. Lists9.4. Sets9.5. Queues9.6. The Collections Class9.7. Maps9.8. Choosing My Collection
10. Lambda Expressions10.1. Introduction10.2. What is a Lambda Expression?10.3. Functional Interfaces10.4. Local Variables in Lambda Expressions10.5. Standard Functional Interfaces10.6. Sorting with Lambdas
11. Streams11.1. Introduction11.2. Pipelines11.3. IntStream11.4. Optionals11.5. Operations
12. Maven12.1. Introduction12.2. Compiling Java12.3. Getting Started12.4. Coordinates12.5. Repositories12.6. Project Object Model12.7. Dependencies12.8. Standard Directory Layout12.9. Lifecycles and Phases12.10. Wrapper12.11. Archetypes12.12. Maven and Git12.13. Common Maven plugins
13. Testing13.1. Introduction13.2. Getting Started with JUnit 513.3. Basics of JUnit 513.4. JUnit Lifecycle API13.5. Expected Exceptions13.6. Timeouts13.7. Nested Tests13.8. Repeating Tests13.9. Third-party Assertion Libraries13.10. FIRST Properties of Good Tests13.11. What to Test: The Right-BICEP13.12. Boundary Conditions: The CORRECT Way
14. Regular Expressions14.1. String Manipulation14.2. Writing Regular Expressions14.3. Using Regular Expressions in String Methods14.4. Regex API
15. Design Patterns15.1. Instructions15.2. What is a Design Pattern?15.3. Gang of Four Design Patterns
16. I/O16.1. File manipulation16.2. I/O Streams16.3. Reading: FileReader and BufferedReader16.4. Reading: Scanner16.5. Reading: Files16.6. Writing Text Files
17. Serialization17.1. Introduction17.2. CSV17.3. JSON17.4. Reading and writing JSON with Jackson17.5. Binary serialization
18. Multithreading18.1. Concurrency18.2. Processes & Threads18.3. Multithreading in Java18.4. Thread Synchronization18.5. Thread Signaling
12. Maven
Programming Project 2021/22

12.1. Introduction

What is Maven?

Maven is a package manager and a build tool for Java.

It is an open source project managed by the Apache Software Foundation.

It was first released in 2004, which means that:

  • It is almost 20 years old!
  • It solves a real problem developers have.
  • It is stable and trustworthy.

Maven is of the most popular build tools for Java, as reported in:

Read more at https://maven.apache.org/what-is-maven.html.

Why Maven?

Maven's main objective is to allow a developer to comprehend the complete state of a development effort in the shortest period of time.

It does that by:

(1) Making the build process easy.

  • Maven will shield you from many details,
  • but it doesn’t eliminate the need to know about the underlying mechanisms.

(2) Providing a uniform build system.

  • Maven builds a project using its project object model (POM) and a set of plugins.
  • If you understand how one Maven project works, you know how all of them work.

(3) Providing quality project information, such as

  • change-log created directly from source control,
  • dependencies used by the project,
  • unit test reports including coverage.

(4) Encouraging better development practices.

  • Standard directory layout.
  • Good testing practices with
    • separate test source code,
    • naming conventions to locate and execute tests,
    • test cases that setup their environment.

What is a package manager?

A package manager is a tool that automates the process of installing, upgrading, configuring, and removing software programs and libraries from a computer system in a consistent manner.

System-level package managers.

Application-level package managers.

You can find a list of package managers here.

Why use a package manager?

  1. We want to reuse someone else's code.
  2. We want to share our work with others.
  3. We don't want to store large binary files in our git repository.
  4. We need help to handle complex dependency trees as projects get more complex.
  5. We want to easily find and download the packages we need.
  6. We want to easily understand which packages (and their specific versions) a project uses. Package managers establish a shared convention for managing libraries.
  7. We want to compartmentalize the installation of dependencies.

StackExchange

What is a build tool?

A build tool is a program that automates the creation of executable applications from source code.

Build automation is the act of scripting tasks that developers do in their day-to-day activities, such as

  • downloading dependencies,
  • compiling source code into binary code,
  • running tests,
  • packaging binary code,
  • deploying to production systems.

Examples of build tools.

You can find a list of build automation tools here.

StackOverflow

Why use a build tool?

In a small project, you may not need one, as you can simply invoke the build process manually. When projects get larger, this is not practical.

  1. We want to keep organized what needs to be built, in what sequence, and the dependencies needed.
  2. We want a quick and consistent build process.
  3. We want easy to build projects.
  4. We want to use our own IDEs.
  5. We want to implement continuous integration and delivery pipelines.

This is how easy it to build a project using Maven.

mvn package

StackOverflow

What is good about Maven?

  1. Quick project setup: convention over configuration.
  2. Modular projects.
  3. Mature dependency management.
  4. Mature project build lifecycle.
  5. Robust plugin community.
  6. Very good IDE support, including IntelliJ IDEA, Eclipse, and VS Code.

What is not so good about it?

  1. The use of XML to describe projects
    • XML is generally disliked due to its hard-to-read syntax.
    • The project description file becomes very big, very quickly.
  2. Maven is harder to extend than Gradle.
  3. Maven is slower than Gradle.

Maven, a de facto standard

Maven established "standards" that are used by other build tools.

  • Maven standard directory layout
  • Artifact naming
  • Artifact repository

Our goal with this module

Our main goal is for you to learn the basic concepts related to package managers and build tools.

A considerable part of this knowledge is transferable to other tools that you may use in the future, such as Gradle, npm, and Grunt.

Understanding Java's build process is valuable for those venturing into the DevOps world.

We do not expect you to be a Maven guru.

You will have to use Maven in your course project.

PreviousNext