In previous chapters, we have seen how to set up Apache Maven to build software projects. We have also seen how to configure it to analyze code quality and code coverage. We have seen how to generate and publish project documentation.

As we use Apache Maven, we will encounter requirements that are not generic, but at the same time, not rare. In many projects, there would be a need to include additional source or resource folders. We will see how Maven allows us to do this. We would also want to get more verbose output from Maven to help troubleshoot when things go wrong. We will also see to what extent we can get the Maven build working without the Internet. We will also see how Maven works with software configuration management (SCM) systems and allows SCM changes to be part of project documentation.