Building projects with Maven and pulling down all of your needed JARs is so convenient, you might forget that the real goal of Maven is to manage projects, in accordance with widely held best principles. And to manage a project effectively, you have to be able to know what's going on.
This excerpt from Maven: A Developer's Notebook is the first in a two-part series on Maven's reporting and publishing tools. In this excerpt, you'll learn how to use the reports for mailing lists, project members, issue tracking, and dependencies. You'll also see the reports generated for test results and code checking. Finally, you'll learn how to aggregate all of these into a single project quality dashboard.
As with all books in the Developer's Notebook series, you'll get the information in a straightforward, factual style, with the details you need to get the job done. In other words: "All lab, no lecture."
Check back next week for part two, which looks at tracking project changes and releases, reporting releases, and publishing your project website.
Download Part 1 of Chapter 4 from Maven: A Developer's Notebook (PDF, 590 KB).
View catalog information for Maven: A Developer's Notebook
Return to ONJava.com.
Copyright © 2009 O'Reilly Media, Inc.