This review is about Sonatype’s Maven: The complete reference by Tim O’Brien, John Casey, Brian Fox, Jason Van Zyl, Eric Redmond and Larry Shatzer.
Disclaimer: I learned Maven from Sonatype’s site 3 years ago. I found it was a great tool to learn Maven. Now that I have a little more experience in the tool, I tried to write this review in an objective manner.
- 13 chapters, 267 pages, free (see below)
- This book is intended for both readers who wants to learn Maven from scratch and for readers who need to look for a quick help on an obscure feature
- A whole chapter is dedicated to the Maven assembly plugin
- Another chapter is dedicated to Flexmojos, a Sonatype plugin to manage Flex projects
- First of all, this book is 100% free to view and to download. This is rare enough to be state!
- Complete reference books are sometimes a mere paraphrase of a product’s documentation. This one is not. I do not claim I’m a Maven expert but I did learn things in here
- This book is up-to-date with Maven 2.2. For example, it explains password encryption (available since Maven 2.1.0) or how to configure plugins called from the command line differently using
default-cli (since Maven 2.2.0)
- A very interesting point is a list of some (all?) JEE API released by the Geronimo project and referenced by
artifactId. If you frown because the point is lost on you, just try using classes from activation.jar (
javax.activation:activation): you’ll never be able to let Maven download it for you since it is not available in the first place for licensing reasons. Having an alternative from Geronimo is good, knowing what is available thanks to the book is better
To be frank, I only found a problem with Maven: The complete reference. Although a whole chapter is written on the Maven Assembly plugin, I understood nothing from it… The rest of the book is crystal clear, this chapter only obfuscated the few things I thought I knew about the plugin.
This book is top quality and free: what can I say? If you’re a beginner in Maven, you’ll find a real stable base to learn from. If you need to update your knowledge, you will find a wealth of information. If you’re a Maven guru, please contribute to the Assembly plugin’s chapter. I can only give a warm thank you for Sonatype’s effort for giving this quality book to the community.
I was contacted last week by Packt Publishing. They made me the following offer: I was to choose the books I wished in their catalog and then write an article for each of them.
I gave this offer much thought and finally said yes on the condition I was to be free to say what I really thought about the book. Since I’m not known for my soft stances on many subjects, I’m really looking forward to write my first article; first, to evaluate the book’s material in itself and second, to see whether Packt will really play the game.
I’m expecting the delivery of 2 books right now:
So expect to see these book reviews in a couple of months. I promise to really speak my mind, whether good or bad and to be straight (but fair). Ok, this may sound exaggerated but I’m really serious about it. Since I happened to stumble upon a PDF chapter of the Maven’s book some time back, and found very interesting plugins in it I did not know about, I have very high expectations. I also am currently writing my first Flex front-end so these two themes are dear to me.
I was asked to put free chapters for each book for download so here they are:
If you have something to say about this new orientation, please do so.
A design pattern in architecture and computer science is a formal way of documenting a solution to a design problem in a particular field of expertise.
Design patterns are a common reference in our line of work. People who discuss a pattern often draw strange looks from people who don’t about it (or who don’t know about patterns in general). Of course, there are dozens and dozens of design patterns just waiting for us to know them.
IMHO, today, the three following books are enough to resolve 99% of our architect’s everyday problems:
- First, of course, is the Gang of Four’s Design Patterns Elements of Reusable Object-Oriented Software. This one was the one which materialized the concept of Design Pattern itself and structured them in categories (creational, structural and behavioral). A must have for anyone dealing with software design in general.
- If one works in JEE environments, one should also have Core J2EE Patterns Best Practices and Design Strategies. According to me, this one is much less important because much of what is exposed relates to EJB2. Thus, these are not Design Patterns per se but methods to overcome the shortcomings of the technology. The patterns are no more relevent if one uses EJB3.
- Finally, with the maturity of ESB finally coming (thanks to SOA), a whole new category of Design Patterns has emerged, namely Messaging Design Patterns. This is covered by Enterprise Integration Patterns. I’m in the process of reading it, but I think it may be the new GOF.
The whole thing is not to know each Design Pattern by heart. But, if you know the general idea and the problems each solves, you can then dwelve further and look how it can be applied in these reference books (or online).
Do you know any other fundamental book about Design Pattern?