src/main/filters – contains files that inject values into configuration properties in the resources folder during the build phase.src/main/webapp – for web applications, contains resources like JavaScript, CSS, HTML files, view templates, and images.src/main/resources – configuration files and others such as i18n files, per-environment configuration files, and XML configurations.src/main/java – Java source code for the artifact.Anything that is supposed to be part of an artifact, be it a jar or war, should be present here. Src/main is the most important directory of a Maven project. maven-project/src/assembly – assembly configuration for packaging binaries.maven-project/src/site – site documentation created using the Maven Site Plugin.maven-project/src/it – usually reserved for integration tests used by the Maven Failsafe Plugin.

maven-project/src/test – holds all the test code and resources.maven-project/src/main – contains source code and resources that become part of the artifact.maven-project/NOTICE.txt – information about third-party libraries used in the project.maven-project/README.txt – summary of the project.maven-project/LICENSE.txt – licensing information of the project.maven-project/pom.xml – defines dependencies and modules needed during the build lifecycle of a Maven project.This directory serves as the root of every Maven project.įollowing are the standard files and subdirectories that are typically found at root: The default directory layout can be overridden using project descriptors, but this is uncommon and discouraged. Directory LayoutĪ typical Maven project has a pom.xml file and a directory structure based on defined conventions: └───maven-project Here we’ll be following standard directory layout of a typical Maven project. So promoting a uniform directory structure across projects is also one of its important aspects. API, service, data access, test, etc.) so that it’s very easy to reason about it. The ultimate solution is to develop small software: divide the whole stack into self-contained components that don’t share files with others, each constitutes very few files (e.g. Instead, partition your code into components, each gets its own folder or a dedicated codebase, and ensure that each unit is kept small and simple. The pitfall of a large application is maintaining a huge code base with hundreds of dependencies – such a monolith slows down developers as they try to incorporate new features. In this blog, we will discuss in detail about the best practices to follow while coding Java based applications.

Java sample source code