sguillory6's dashboard

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"

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.

sguillory6 reported a problem in Sonatype on July 02, 2008 04:56:

Grammatical error in first paragraph of section 8.4

In the first paragraph of section 8.4, the following sentence occurs:

Most complex Maven multi-module projects tend to define all version
in the top-level POM.

Don't know what exactly you want to say here, but the singular form of the word "version" is almost certainly not correct.

sguillory6 reported a problem in Sonatype on July 02, 2008 04:43:

Typo on page 147

In the first paragraph at the top of page 147, the sentence:

This is often the case when a project's release consists of several closely coupled
component.

uses the singular form of "component". It should use the plural form.

sguillory6 reported a problem in Sonatype on July 02, 2008 04:37:

Grammatical error in first paragraph of chapter 8

In the first paragraph of section 8.1, there is a grammatical error in the sentence:

Maven is a very capable and tool which can be as simple or as complex
as you need it to be.

The first instance of the word "and" should be removed.

sguillory6 reported a problem in Sonatype on July 02, 2008 03:43:

Typo on page 127, chapter 7

On page 127, chapter 7, the sentence:

In other words, we
have out Hibernate mapping

uses the word "out", instead of "our".

sguillory6 reported a problem in Sonatype on July 01, 2008 20:24:

Type on page 106, chapter 7

The last sentence on page 106 reads:

A textual description of
conditions, the temperature, and the data of the observation is stored in a
Condition class.

The word "data" should be "date"

sguillory6 replied on July 01, 2008 15:42 to the problem "Unit tests for chapter 4 don't build. Missing dependency on commons io" in Sonatype:

Actually, I guess this is okay. In section 4.8, you haven't actually added the unit tests yet. I had all the test source in place when I was going through section 4.8. If you follow along exactly in chapter 4, things should be okay.

sguillory6 replied on July 01, 2008 15:39 to the problem "Unit tests for chapter 4 don't build. Missing dependency on commons io" in Sonatype:

I realize the you do add this dependency in section 4.10, but you imply in section 4.8 that the "mvn install" goal will succeed. It won't since the build of the unit tests fail.

sguillory6 reported a problem in Sonatype on July 01, 2008 15:26:

Unit tests for chapter 4 don't build. Missing dependency on commons io

The unit tests for the example in chapter 4 depend on apache commons io, which is not specified in the pom. I had to add the following to the pom:

<dependency>
<groupid>org.apache.commons</groupid>
<artifactid>commons-io</artifactid>
<version>1.3.2</version>
<scope>test</scope>
</dependency>

sguillory6 reported a problem in Sonatype on July 01, 2008 15:15:

Example in chapter 4 does not build w/o pom changes

The example in chapter 4 requires java 5 since generics are used in the YahooParser class. However, the pom has not been modified to assume 1.5 source, so the build fails.

sguillory6 reported a problem in Sonatype on June 30, 2008 23:47:

Punctuation error in section 3.5.5

There is a punctuation error in section 3.5.5, in the last paragraph on page 43. The sentence reads:

"When creating a JAR for a project, dependencies will not be bundled with the
generated artifact they are only used for compilation."

There should probably be a comma between the words "artifact" and "they".

sguillory6 reported a problem in Sonatype on June 30, 2008 23:44:

Grammatical error in section 3.5.5

There is a grammatical error in the third paragraph of page 43 of section 3.5.5. The sentence reads:

Transitive dependencies
can come in handy when your project relies on another projects with several small
dependencies (like Hibernate, Apache Struts, or the Spring Framework).

The word "another" should probably be "other"

sguillory6 reported a problem in Sonatype on June 30, 2008 19:47:

Wrong command listed in section 3.5.2

On page 30 of chapter 3, the reader is asked to run the command "mvn install". Later, in the first sentence of page 35, the reader is informed that "The second command we rean in the previous section was mvn package."

sguillory6 shared an idea in Sonatype on June 26, 2008 20:46:

Criticism of Ant in Section 1.2 not accurate

On page 2, section 1.2, second paragraph, you write:

While this might seem
trivial, consider the fact that most Ant-based builds have to define the locations of
these directories in every subproject.

I don't think anyone with experience with Ant 1.6 or greater would design a build this way. Most organizations define a common source code layout, all common build tasks are placed in a master build file that defines these locations in a master property file.

The build files for individual projects typically contain little more than an import of the master build file. And of course the local build file can utilize a local property file before the import to override any values in the master property file.

I'm not saying ant is better than maven. Just suggesting that your criticism of ant isn't really accurate.

sguillory6 reported a problem in Sonatype on June 26, 2008 20:38:

Grammatical error in section 1.2

There is a grammatical error on page, last sentence of first paragraph. It reads:

If you
don't care follow convention, Maven will allow you to customize defaults in order
to adapt to your specific requirements.

and probably should read:

If you
don't care *to* follow convention, Maven will allow you to customize defaults in order
to adapt to your specific requirements.