sguillory6's dashboard

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 14:02 to the question "Missing punctuation in section 17.4.4" in Sonatype:

Stan, thanks again. I just committed this change.

sguillory6 asked a question in Sonatype on August 27, 2008 14:27:

Missing punctuation in section 17.4.4

Missing punctuation in section 17.4.4, page 514. Near the top of the page, the text "you might want
to just print a warning message and move on Warnings are not fatal" is missing a period. It should read

you might want
to just print a warning message and move on. Warnings are not fatal,

sguillory6 replied on August 26, 2008 05:58 to the question "Execution of example maven plugin goal is backwards" in Sonatype:

Also, the text does not mention that you have to run "mvn clean install" after adding the goalPrefix to the pom to make the goalPrefix available.

sguillory6 asked a question in Sonatype on August 26, 2008 05:56:

Execution of example maven plugin goal is backwards

After configuring a goalPrefix of "blah", the text on page 465 claims that you can run the echo goal with "mvn echo:blah". It is actually "mvn blah:echo"

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.

mavenbook replied on August 22, 2008 09:53 to the problem "Typo on page 127, chapter 7" in Sonatype:

Fixed, out changed to our. Again Stan, you are providing an invaluable service.

mavenbook replied on August 22, 2008 09:51 to the problem "Grammatical error in first paragraph of chapter 8" in Sonatype:

Fixed

mavenbook replied on August 22, 2008 09:38 to the problem "Typo on page 147" in Sonatype:

Fixed, components is now plural.

mavenbook replied on August 22, 2008 09:36 to the problem "Grammatical error in first paragraph of section 8.4" in Sonatype:

Fixed in trunk, I changed it to:

"Most complex Maven multi-module projects declare all versions in the top-level POM making the top-level POM a focal point for changes that affect the entire project."

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.

kirlich started following the problem "Wrong command listed in section 3.5.2" in Sonatype.

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.

Alexandre replied on August 05, 2008 17:43 to the problem "Example in chapter 4 does not build w/o pom changes" in Sonatype:

It's needed to add this into pom.xml:

<build>
<plugins>
<plugin>
<groupid>org.apache.maven.plugins</groupid>
<artifactid>maven-compiler-plugin</artifactid>
<configuration>
<source>1.5</source>
<target>1.5</target>
</configuration>
</plugin>
</plugins>
</build>

sguillory6 reported a problem in Sonatype on July 02, 2008 05:54:

Typo in section 9.4.3

In the first paragraph of section 9.4.3 on page 186, the following sentence occurs:

For example,
you can specify that your project depends on version 3.8 or greater of JUnit, or
anything between version 1.2.10 and 1.2.14 of JUnit

I believe, based on the hypothetical version numbers offered in the second part of the sentence that the last word of this sentence should be "Log4J", not "JUnit".

sguillory6 reported a problem in Sonatype on July 02, 2008 05:25:

Grammatical error in section 9.2.1

In the first paragraph of section 9.2.1, the sentence:

All Maven project POMs extend this Super POM, it defines a set of defaults
shared by all projects.

Should probably be broken into two distinct sentences:

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