mavenbook's dashboard

chris.bedford started following the idea "More Details on Nexus Architecture Please" in Sonatype.

A comment on the discussion "What do you want us to write next?" in Sonatype:

In my opinion it's all about the complexity of your builds. Where I work, we have a ludicrous number of builds, many of which share sub modules with other builds. Managing our dependencies, both internal and third party, would be a nightmare without Maven.

So, I think what you say is true for simple projects with minimal complexity and dependencies, but beyond that, Maven is a clear win. Take a look at some of the open source projects using it and I think you'll see what I mean. – Chris Patti, on September 26, 2008 18:49

vocaro replied on September 25, 2008 20:34 to the discussion "What do you want us to write next?" in Sonatype:

How about a Maven Cookbook? Something analogous to the Rails Cookbook. Instead of a tutorial with reference material, it would be a list of self-contained "recipes" for solving specific problems with Maven.

Matt Gumbley marked one of mavenbook's replies in Sonatype as useful. mavenbook replied to the problem "Typo in Common Environments.".

mavenbook replied on September 01, 2008 16:44 to the question "maven: Error reading assemblies" in Sonatype:

Are you referencing the assembly from your pom?

It is tough to diagnose your issue without seeing a full example. I've made a note to supply a straightforward example of a custom assembly descriptor in the first part of the book.

mavenbook set one of mavenbook's replies as an official response to "Typo on Ex 17.5" in Sonatype

mavenbook replied on September 01, 2008 16:36 to the problem "Typo on Ex 17.5" in Sonatype:

Steve, it was worse than that, the closing element was "pluginGroupd". I fixed it. Thanks, I also added your name to the preface on the online book.

mavenbook replied on September 01, 2008 16:18 to the problem "Wrong command listed in section 3.5.2" in Sonatype:

I made sure to change references to "mvn package" to "mvn install". Thanks again Stan.

mavenbook replied on September 01, 2008 16:10 to the problem "Grammatical error in section 3.5.5" in Sonatype:

Ok, I changed "another" to "other". Thanks again Stan.

mavenbook replied on August 31, 2008 17:46 to the problem "Wrong output text building Apache Shindig as example." in Sonatype:

I updated the output to reflect that Maven is trying to get to the local Nexus instance. Your output is going to vary on this example a bit as Shindig is a moving target, but I didn't verify that the steps outlined in this chapter do allow you to build Shindig after adding the two missing Maven repositories.

Thanks for the note.

mavenbook replied on August 31, 2008 14:38 to the problem "4.8.1 exec plugin now supports -Dexec.args=..." in Sonatype:

Great, thanks for the note. I've added in a section to 4.8 about passing in another Zip Code.

mavenbook shared an idea in Sonatype on August 31, 2008 14:05:

More Details on Nexus Architecture Please

I'd like to know more about how Nexus was designed. What is the underlying architecture? How is the data stored locally? What is the format of the Nexus index?

mavenbook replied on August 31, 2008 14:02 to the question "Missing punctuation in section 17.4.4" in Sonatype:

Stan, thanks again. I just committed this change.

mavenbook replied on August 31, 2008 14:00 to the problem "Incomplete session 16.5.5." in Sonatype:

I added a bullet point about "Synchronize Shadow Repository" to the setion that deals with Scheduled Services. As I was in there, I also noticed that we weren't saying anything about the Empty Trash service.

Thanks velo.

mavenbook set one of mavenbook's replies as an official response to "Typo in Common Environments." in Sonatype

mavenbook replied on August 31, 2008 13:29 to the problem "Typo in Common Environments." in Sonatype:

Thanks for being picky. I added the missing article.

The other core motivations were world domination and an easy way to support multiple deployment environment. Honestly, I'm not sure, I think I remember writing this particluar section on a 747 flying from New York to Chicago in some severe turbulence, so maybe I was a bit distracted.

Not a satisfying answer, but thanks for catching this. The copy edit for print caught this, but I didn't take that particular paragraph back into the print version of the book.

mavenbook set one of mavenbook's replies as an official response to "17.4.2 A Simple Mojo -- missing @requiresProject false" in Sonatype

mavenbook replied on August 31, 2008 13:24 to the problem "17.4.2 A Simple Mojo -- missing @requiresProject false" in Sonatype:

Pat, thanks for reporting this, I've added this annotation to the ch17 EchoMojo example, and I've updated the online book.

mavenbook replied on August 22, 2008 10:01 to the problem "Unit tests for chapter 4 don't build. Missing dependency on commons io" in Sonatype:

I thought about how to address this, and was going to put a note in section 4.8 telling people that there could be a failure. In the end, I decided to leave it alone because the reference to a future section seemed more confusing.

I guess I'm just going to assume people read this chapter in order, and also just hope people are working against the downloaded example code.

mavenbook replied on August 22, 2008 09:54 to the problem "Type on page 106, chapter 7" in Sonatype:

data changed to date.