"14.1 ... The m2eclipse project, provides " - superfluous comma.
"14.2. m2eclipse The m2Eclipse plugins (http://m2eclipse.codehaus.org/) provide" - incorrect pluralisation? Should be "The m2eclipse plugin (url) provides" ?
"14.2 ... interact with Subversion repositories ... mylyn... " would it be possible to expand on how m2eclipse uses the repository access it gains from Subclipse? Ditto Mylyn, how is the task-focused UI mediated/changed when m2eclipse is used?
"14.3.1 ... agree to the plugin license" should read "agree to the plugins' licenses".
In the provided settings.xml snippet, configuration for 'releases' is duplicated. On of them should most likely be changed to say 'snapshots' to relate better to the text "When you attempt to deploy to a server with an identifier of releases or snapshots...". That text should probably also include the thirdparty identifier as it is included in the settings.xml example.
The second paragraph of section 16.7 (v0.14 of the book) incorrectly states that Nexus does not provide for any security for hosted repositories. However, in section 16.7.1 it is explained how to configure user name and password for deployment. That paragraph should be updated to correctly state the security provided in Nexus beta5.
In section 16.4 of v0.14 of the book, I've found that the following confuses me:
* Section 16.4.1: The text "Once you've configured Nexus to be the mirror for all repositories, Maven will now consult the local installation of Nexus instead of going out to the central Maven repository." is confusing. When I first read it, I thought that it was directly related to example 16.1 which it isn't as in example 16.1 Nexus is only the mirror of central. Secondly, the part "instead of going out to the central Maven repository" is incorrect if we're talking about settings up a mirrors for ALL repositories. Thirdly, it's talking about configuring Nexus while the section is regarding how Maven should be configured to use Nexus as a mirror. Some kind of re-phrasing is needed.
* Section 16.4.1: "After you've run a few builds against your local Nexus installation, you can then start to browse the contents cached in your local instance of Maven." should most likely be changed to "...you can then start to browse the artifacts cached in Nexus.".
* Section 16.4.2: I guess that "...will allow you to use the Nexus public group which resolves artifacts from four repositories..." talks about the default configuration of Nexus as it might not be true for an altered configuration. Some remark regarding this would be good.
* The title of section 16.4 is "Configuring Maven to Use Nexus Repositories". However, sections 16.4.3 and especially 16.4.4 and 16.4.5 is regarding configuring repositories in Nexus. Either the title should be changed or the sections moved/rearranged.
In section 16.3.4 of v0.14 of the book, "...load the RSS feed in your browse and..." should read "...load the RSS feed in your browser and..."..
Also, it states that there are "six system feeds". Unless there are different types of feeds, there are seven system feeds. If in fact only six of the seven feeds are SYSTEM feeds, and one of the feeds is of some other type, this should be clarified.
In Nexus 1.0 beta-5, the path for wrapper.log is ${NEXUS_HOME}/logs/wrapper.log, not ${NEXUS_HOME}/container/logs/wrapper.log as stated in section 16.2.3.
When referring to a plugin goal, we frequently use the shorthand notation: pluginId:goalId. For example, when referring to the create plugin in the Archetype plugin, we write archetype:create.
Shouldn't that be:
When referring to a plugin goal, we frequently use the shorthand notation: pluginId:goalId. For example, when referring to the create goal in the Archetype plugin, we write archetype:create.
Add integration with a service like Get Satisfaction that will allow readers to post ideas, ask questions, and identify problems with the book. A book is much more than a set of static words, it can serve as the meeting place for a community. A book is also very much "alive" in the sense that it has to react to what the readers need. Since this book is never going to be "finished" in the sense of a traditional book, why not integrate Get Satisfaction to provide a forum for reader?
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.
Loading Profile...
mavenbook (Official Rep)
last replied
on September 01, 2008 16:36
Anders Hammar
last replied
on August 13, 2008 12:08
EMPLOYEE
