Understanding the standard directory layout

When we built our sample Java project earlier, we saw files being compiled, tests being run, and a JAR being generated. We do not know where these artifacts were created.

How to do it...

Let's find where the artifacts were created by performing the following steps:

1. Go to the folder that has the sample Maven project.

2. Open the target subfolder that was created:

   

How it works...

When Maven runs, it puts all the contents that it generates into a separate folder. This is to distinguish it from any user-generated content. Let us examine the contents of this folder:

• The classes folder: Compiled source files are placed in this folder. This folder will also contain resources, such as XML and property files that are part of the source, placed in src/main/resources.

• The test-classes folder: Compiled test source files are available in this folder. In addition, it also contains test resources, which are files required for the purpose of testing, but not for running the project.

• The surefire-reports folder: Test reports are separately placed in this folder. Typically, both XML and HTML report formats are available. The latter can be opened in the browser, while the former can be integrated with a code coverage tool.

• The output .jar file: The generated project artifact is also present in this folder.

• Two other folders—maven-archiver and maven-status—hold information used by Maven during the build.