From the course: Introducing Maven

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

The Java project structure

The Java project structure

From the course: Introducing Maven

Start my 1-month free trial

The Java project structure

- [Instructor] The Java project structure for Apache Maven is one of those areas that tends to be polarizing among Java developers. While Maven will argue that the file structure requirements are in place on purpose to help you build your code following best practices, there are arguments against it in the community. While some call this a pain point, I would argue on the side of Apache that this is a great separation. But as I alluded to, it is a source of complaints when it comes to Apache Maven. Consider however that this structure cleanly separates code from the resources that the project needs to operate. Things like property files, logging instructions, and other non-Java code files. It also separates live code from test code, which makes your code easier to navigate than say something like Go where the test lives right next to the files they are testing. This separation makes it infinitely easier to read code versus tests and if you maintain package structure, finding tests…

Contents