Maven as a build tool has become the de-facto standard over the years. It's not surprising if we look a little deeper into what Maven brings. Maven has two primary features and they are:
- Convention over configuration: Tools built prior to Maven gave developers the freedom to choose where to put source files, test files, compiled files, and so on. Maven takes away this freedom. Because of this, all the confusion about locations also disappears. In Maven, there is a specific directory structure for everything. The following table shows a few of the most common locations:
| Source code in Scala |
| Source code in Java |
| Resources to be used by the source code, such as configuration files |
| Test code in Scala |
| Test code in Java |
| Resources to be used by the test code, such as configuration files |
- Declarative dependency management: In Maven, every library is defined...