mavenbook's dashboard

mavenbook replied on August 22, 2008 09:26 to the problem "Grammatical error in section 9.2.1" in Sonatype:

Fixed in the trunk, publishing later on today. Thanks for catching this. I changed the sentence to:

All Maven project POMs extend the Super POM which defines a set of defaults shared by all projects.

mavenbook replied on August 06, 2008 15:52 to the problem "Homophonic Error in Section 1.6" in Sonatype:

Thanks for catching this, I'm a whorable spelr.

mavenbook replied on August 06, 2008 15:50 to the problem "Section 1.6: Typo with "?" in place of ","" in Sonatype:

Fixed in trunk, should be pushed out later on today.

Thanks for catching the typo, I reread that paragraph and change some of the language, it was over the top. A bit too dramatic.

mavenbook replied on August 06, 2008 15:45 to the problem "Example in chapter 4 does not build w/o pom changes" in Sonatype:

I've added explicit compiler settings to all of the ch04-ch07 examples. This was happening because the example projects were depending on the Sonatype Forge POM.

mavenbook replied on August 06, 2008 15:31 to the problem "Typo in section 9.4.3" in Sonatype:

Just another posting, I forgot to mark the issue as solved.

mavenbook replied on August 06, 2008 15:30 to the problem "Typo in section 9.4.3" in Sonatype:

Good catch, I fixed this in trunk, should be pushed to the site in the next day with the Nexus update.

mavenbook replied on June 29, 2008 21:15 to the idea "Integrate Get Satisfaction and Gather Reader Input" in Sonatype:

We did it, and, with hindsight, it was a good move. hopefully more of you will signup and contribute.

mavenbook replied on June 29, 2008 21:14 to the problem "Code Examples in PDF Version of Book Too Wide" in Sonatype:

Despite the fact that our current PDF build is missing all figures, if you download the PDF, you'll notice that all code examples now fit within the width of the code boxes.

mavenbook reported a problem in Sonatype on June 29, 2008 21:13:

All Figures Missing from the PDF

Due to a problem with the PDF generation, there are currently no figures in the PDF. We regret this inconvenience, and are currently working to address this problem. In the meantime, we ask that you use the online HTML version of the book.

mavenbook started a conversation in Sonatype on June 29, 2008 19:26:

What do you want us to write next?

What do you want us to write next? We're wondering if, you, the reader, have any input into what you are looking for when it comes to Maven documentation. Are you looking for a more task-centric book like a Cookbook? Or, are you looking for longer tutorials? Please let me know, we're also interested in known what specific areas of Maven documentation you think could use more attention.

mavenbook replied on June 29, 2008 19:24 to the problem "XML tags incorrect on EX 11.10" in Sonatype:

Thanks for pointing out this typo, I just updated the source for the book, and I'll be pushing a revision up to the site in the next few minutes.

Thanks again.

mavenbook replied on June 29, 2008 19:03 to the problem "Grammatical error in section 1.2" in Sonatype:

Great, thanks for bringing this to or attention (and thanks for being one of the first to use this Get Satisfaction tool). I just fixed it in SVN and I'm going to be pushing the live site in a bit.

mavenbook replied on June 29, 2008 19:01 to the idea "Criticism of Ant in Section 1.2 not accurate" in Sonatype:

Right, I see where you are coming from, and I acknowledge that the statement (as written) is a bit confusing. What I'm really trying to say is that Ant doesn't ship with any assumptions or conventions and that the main difference between Ant and Maven is that one has to supply explicit directory locations to Ant where the same build in Maven could just follow convention.

I've updated the section to read:

While this might seem
trivial, consider the fact that most Ant-based builds have to
define the locations of these directories. Ant doesn't ship with
any built-in idea of where source code or resources might be in a
project; you have to supply this information.

mavenbook replied on June 29, 2008 18:53 to the idea "Nexus Packaging" in Sonatype:

Hello Israel,

We've had other people ask us for this feature before, and while we're not currently focused on providing stand-alone WAR support, there is an issue in our JIRA about this. If you want us to focus on this issue, we ask that you vote for the issue. You can do so by registering for a JIRA account and clicking on the vote link for http://issues.sonatype.org/browse/NEXUS-58.

Follow, this thread on the Nexus developer mailing list. In his reply, Jason says:

We focus a good block of our time on user issues which have the highest votes. You can talk about it on the mailing list but the vote count is what drives us. Like everything, if you want things changed you have to vote.

mavenbook replied on June 29, 2008 18:46 to the idea "Help Us Get the Word Out about Nexus" in Sonatype:

One problem we've noticed is that people might not be aware that the best practice in Maven is to run a proxy between you and the public repository. It really does enable a whole different level of use with Maven. Allowing you to deploy your own artifacts and have some control over what is being downloaded from the Central repository. When you run Sonatype Nexus, and you configure a mirror, Maven is going to consult Nexus whenever it needs to locate an artifact. If Nexus doesn't have the artifact it is going to retrieve it and the cache the result for the next person to request the same artifact.

Nexus really speeds up Maven builds as your Maven instance is going to be hitting a local, dedicated resource and not the shared resource that is the Central Maven repository. If you run into someone who is complaining that Maven's interaction with the Central Repository is slow, you should let the know that the best way to solve the problem is to download Sonatype Nexus.

You can learn more about Sonatype Nexus at the Sonatype Nexus Pages on the Sonatype web site.

Oh and thanks cjodea.

mavenbook shared an idea in Sonatype on June 29, 2008 18:46:

Help Us Get the Word Out about Nexus

@akohli get a proxy in place. Have been using sonatype nexus and it does a very good job

mavenbook replied on June 29, 2008 18:38 to the problem "Settings.xml properties don't activate profiles." in Sonatype:

Jamie, let me do some checking and testing on my side. This could be due to the fact that I was using 2.1 for portions of the book. Until 2.1 is officially released, I've gone back to using the latest 2.0.9 release. I'll let you know what I find after I ping Brian Cox about this.

Thanks again for pointing this out.

mavenbook replied on June 29, 2008 18:34 to the problem "XML tags incorrect in Example 11.9 (activating profiles)" in Sonatype:

Jamie, good catch, I've updated the profiles chapter to reflect your corrections:

Online HTML: http://www.sonatype.com/book/reference/profiles.html#d0e11228

PDF: http://www.sonatype.com/book/pdf/maven-definitive-guide.pdf

mavenbook replied on June 04, 2008 16:47 to the problem "Wrong configuration file in 17.5.2. Multi-valued Mojo Parameters" in Sonatype:

Alright, ecamacho (of javahispano.org?). I've fixed this typo. The example now has the appropriate element. Thanks for the feedback.

mavenbook reported a problem in Sonatype on June 04, 2008 06:33:

Code Examples in PDF Version of Book Too Wide

The code examples in the PDF are overflowing to the RHS of the page. It looks very sloppy, could you fix it?