Let's proceed on our journey. In this chapter, we will start with the Maven project structure followed by the build architecture, then we will cover some essential concepts, and finally learn how to create simple Maven projects. The chapter is divided into the following sections:
Maven, as stated in earlier chapters, follows convention over configuration. This makes us believe that there is a standard layout of the Maven project structure. Before we get into creating and playing with Maven projects, let's first understand the basic common layout of Maven projects, as follows:
Folder/Files |
Description |
---|---|
|
This contains an application's Java source files |
|
This contains files of an application's resources such as images, sounds, templates, and so on |
|
This contains the resource's filter files |
|
This contains the configuration files of the application |
|
This has files of application-specific scripts |
|
This has sources files for web applications |
|
This contains unit test files of Java |
|
This has unit testing-specific resources used in an application |
|
This has files of the test-specific filter for resources |
|
This has integration tests files (primarily for plugins ) |
|
This contains files of the assembly descriptors |
|
This contains site artifacts |
|
This denotes the projects license |
|
This includes the notice and attributions that the project depends on |
|
This denotes the project's readme information |
|
This houses all the output of the build |
|
This is the project's |
Though the previously mentioned layout is the standard recommended convention, this can always be overridden in the project descriptor file (pom
file).
3.138.37.20