Maven: The Definitive Guide Split into Two Books
By Tim OBrien
2 minute read time
Maven: The Definitive Guide has been split into two separate books: Maven by Example and Maven: The Complete Reference. The original book had two parts: an example-driven section and a more "referency" section, and each of these sections is now being developed as a separate book. We did this for a number of reasons, but the most important was the idea that a good book has an ideal number of pages. A good introduction should weigh in at around 250 while a more complete reference might easily exceed 400 pages. With this change, we have more than enough room to grow both books over the coming months.
The following books are Part I and Part II of the old definitive guide:
- Maven by Example - This book is an example-driven introduction. If you are new to Maven, read this book first. It will introduce all of the basics and take you all the way up to a multi-module enterprise project.
- Maven: The Complete Reference - Novice or expert, this book will quickly become a dog-eared reference. This book covers topics in depth, including: build properties, the project object model, and other essential aspects of Maven.
If you've bookmarked our book, the existing links will continue to work, but they will automatically redirect to the appropriate book.
DE and ZH Translations
The Chinese and German translations of the book are still combined into a single, two-part book. As we continue to develop the content these translated titles will also be split into two books. In the meantime, enjoy:
OR
Download the German translation of "Maven: The Definitive Guide" as a PDF.
Written by Tim OBrien
Tim is a Software Architect with experience in all aspects of software development from project inception to developing scaleable production architectures for large-scale systems during critical, high-risk events such as Black Friday. He has helped many organizations ranging from small startups to Fortune 100 companies take a more strategic approach to adopting and evaluating technology and managing the risks associated with change.
Explore All Posts by Tim OBrien