By following and completing this chapter, you will be able to take an existing Ant-based build, split it into modular components (if needed), compile and test the code, create JARs, and install those JARs in your local repository using Maven. At the same time, you will be able to keep your current build working. Once you decide to switch completely to Maven, you will be able to take advantage of the benefits of adopting Maven’s standard directory structure. By doing this, you would eliminate the need to include and exclude sources and resources “by hand” in the POM files as shown in this chapter.
Once you have spent this initial setup time Maven, you can realize Maven’ other benefits – advantages such as built-in project documentation generation, reports, and quality metrics.
Finally, in addition to the improvements to your build life cycle, Maven can eliminate the requirement of storing jars in a source code management system. In the case of the Spring example, as Maven downloads everything it needs and shares it across all your Maven projects automatically – you can delete that 80 MB lib folder.
Now that you have seen how to do this for Spring, you can apply similar concepts to your own Ant based build.