First, I’m happy to announce that the Nexus Book is now as open source as our Maven book. We made a decision about a month ago to free this content and make it available for anyone to view the source or modify the book as they see fit. All of our books are covered by […]
With it’s default behavior, Maven runs a plugin invocation for each project in a multi-module build. For plugins that operate on a single project at a time, this is what the author wants.
Some plugins are what we call “aggregators” which means they actually do want all the information about the full multi-module build before execution. These plugins, when run on a tree of projects cause Maven to resolve all the children before calling the plugin’s execute() method. In this mode a plugin executes just once, but effectively on the whole tree at once. (as a side note, you never want to bind an aggregator goal in your pom as this would cause the plugin to run an n! recursive build since the lifecycle would step into each child and execute the aggregator…which would cause Maven to reresolve all the children, etc)
Sometimes neither of those behaviors are what you want.
The goal of this blog is to show an updated and more involved example then what is currently located on the plexus site. This will cover creating a couple of components and explain the different ways to inject your dependencies. This example assumes you are using maven 2 to make your life easier.
We have some new training dates for June-October 2009, and we’re going to be adding some new cities to the mix as well: May 19-20, 2009, Chicago, IL June 9-10, 2009, Mountain View, CA June 23-24, 2009, Chicago, IL July 7-8, 2009, Mountain View, CA July 28-29, 2009, Boston, MA August 4-5, 2009, Mountain View, […]
It escapes me what positive benefit people derive from dumping their accumulated angst with Maven on a blog, but it tends to happen every so often. Each of these posts tends to expose more about the person that wrote the post than about Maven itself. Here’s where I think the most recent post goes wrong:
The nexus indexer has become fairly popular, and is the de-facto standard when it comes to indexing maven repositories (including the big boy, central). As repositories grow and grow, the index of artifacts grows right along with them. What was initially a small few hundred kilobyte file, will grow into 20-30 megabytes or more over […]
We just cut the 0.5 Edition of the book… Download the PDF or Read the Book Online. More readable PDF content. – Typography makes a huge difference to the readability and usability of a text like Maven: The Definitive Guide, and this edition marks a series of editions that are going to focus on bringing […]
Brian Murphy wrote a long blog post about the PAX Plugin which provides a good example of the power of Maven to act as an integration “bridge” between a number of unrelated technologies. In this post, Brian is using the PAX Maven Plugin from ops4j together with the gmaven-plugin and the maven-scala-plugin, he concludes with […]
Just wanted to give people a heads up. The FlexMojos chapter is going to be the focus of the 0.5 release of the Maven book. I got a quick request yesterday for the most recent documentation for FlexMojos 3.1.0, and it motivated me to spend some time on our Flex chapter. If you are a […]
Christopher Judd places Nexus, Hudson, and Maven in his “Ultimate Java Build System” stack: “Now after all these years, I think I found the right solutions for Enterprise Java Builds. The solution involves 5 open source projects: Maven, Subversion, Hudson, Nexus, Sonar.” We’re convinced that Nexus provides the best option for repository management, and as […]