Nexus Book Edition 1.4: SSL Doc, Expanded Install Docs
By Tim OBrien
11 minute read time
Announcing the availability of Repository Management with Nexus, Edition 1.4. Learn Nexus today by:
This edition contains three major changes from Edition 1.3, and a series of smaller changes that are captured in the release notes included at the end of this blog post:
- A new appendix focused on SSL configuration: configuring client-side certificates, configuring Nexus to serve SSL directly, and configuring SSL redirect.
- Expansion of the installation chapter to describe the contents of the various directories created by Nexus.
- Numerous typos, references, and errors fixed in the latest edition of the book.
Repository Management with Sonatype Nexus
The following changes were introduced in Edition 1.4 on August 24,
2009:
- Added instructions for Connecting to a Server with a SSL
Client Certificate in Section C.2, “Importing a SSL Client Certificate” - Added Instructions for Serving SSL Directly from Nexus in
Section C.3, “Configuring Nexus to Serve SSL” (NXBOOK-141) - Added Instructions for Configuring SSL Redirects in Section C.4, “Redirecting Non-SSL Connections to SSL” (NXBOOK-142)
-
Enumerated Trademarks in the Copyright Front matter (NXBOOK-150)
- Defined Sonatype Trademarks in Copyright Front matter (NXBOOK-149)
-
Entire Creative Commons License Added to the Copyright Front
matter (NXBOOK-151) - Added Note Icons to the Nexus Book (NXBOOK-69)
-
Added Figures to the Installation Chapter:
- Figure 2.1, “Downloading Nexus Open Source from
http://nexus.sonatype.org” and Figure 2.2, “Selecting the Nexus Open Source Distribution Download”: screenshots
of the Nexus Open Source Download Page (NXBOOK-171) - Figure 2.3, “Downloading Nexus Professional from
http://www.sonaype.com/products/download”: screenshot of
the Nexus Professional Download Page (NXBOOK-172)
- Figure 2.1, “Downloading Nexus Open Source from
- Updated Section 2.8.1, “Running the Nexus WAR in Glassfish”. (NXBOOK-202
and NXBOOK-144) - Added a note to the end of Section 2.1.1, “Downloading Nexus Open Source” that directs people to the WAR
installation instructions. (NXBOOK-173) -
Added a section describing the contents of the Nexus runtime
directory: Section 2.10.3, “Nexus Runtime Directory”. (NXBOOK-177) - Added a section describing the contents of the Nexus
configuration directory: Section 2.10.2, “Nexus Configuration Directory”. - Added a section describing the contents of the Sonatype Nexus
Work directory: Section 2.10.1, “Sonatype Nexus Work Directory”. (NXBOOK-178) -
Added figures detailing the filesystem after Nexus
installation: Figure 2.14, “The Nexus Professional Runtime Directory”, Figure 2.13, “Nexus Professional Configuration Directory”, and Figure 2.12, “The Sonatype Nexus Work Directory” (NXBOOK-176) - Created two separate sections for installation:
- Adding cross references to the Post-Install Checklist. It
doesn't do much good to tell a new user to go do something and then
not tell them where to look:- Added link to Section 4.8, “Changing Your Password”. (NXBOOK-185)
- Added a section listing Nexus Prerequisites: Section 2.2.1, “Nexus Prerequisites” (NXBOOK-203)
- Added numbers to the post-install checklist steps in Section 2.5, “Post-Install Checklist”. (NXBOOK-188)
-
Added a clarifying note about Nexus listening to all
configured IP addresses on a machine (0.0.0.0) to Section 2.4, “Running Nexus”. (NXBOOK-180) - Added Figure 2.4, “Default Nexus Administrative Credentials (admin/admin123)” to
emphasize the default administrative username and password. (NXBOOK-182)
The following typos and errors were addressed in edition
1.4:
- Fixed a number of dangling cross-references:
- Fixed Dangling Reference in Section 2.8, “Installing the Nexus WAR” (NXBOOK-130)
- Fixed Dangling Reference in Section 9.4, “Performing a Staged Deployment with Maven” (NXBOOK-137)
- Fixed Dangling Reference in Section 9.3.3, “Configuring Staging Profiles” (NXBOOK-136)
- Fixed Dangling Reference in Section 9.6, “Managing Staging Repositories in Nexus” (NXBOOK-138)
-
Fixed Dangling Reference in Section 2.7, “Running Nexus Behind a Proxy” (NXBOOK-129)
- Fixed Dangling Reference in Section 2.5, “Post-Install Checklist” (NXBOOK-128)
- Fixed Dangling Reference in Section 6.3.2, “Nexus Procurement Suite” (NXBOOK-135)
-
Fixed Dangling Reference in Section 5.1.2.1, “Selecting Mirrors for Proxy Repositories” (NXBOOK-133)
- Removed a Dangling Reference from Section 5.1.2, “Managing Repositories” (NXBOOK-132)
- Fixed Dangling Reference in Section 5.1.3, “Managing Groups” (NXBOOK-134)
-
Fixed Dangling Reference in Section 4.4, “Searching for Artifacts” (NXBOOK-131)
- Removed a Dangling Reference from Section B.2.1, “Migrating an Archiva Managed Repository” (NXBOOK-139)
- Fixed an wrong caption for Figure 2.5, “Nexus Application Window (default login/password is
admin/admin123)” (NXBOOK-183) - Fixed a bad script name in Section 2.6.1, “Startup Scripts for Linux”. (NXBOOK-181
and NXBOOK-189) - Removed all DocBook link elements. (NXBOOK-155)
- Minor rewording in Section 2.6.1.1, “Add Nexus as a Service on Redhat, Fedora, and CentOS”. (NXBOOK-199)
- Rewording in Section 2.7, “Running Nexus Behind a Proxy”.
(NXBOOK-192) -
Removed stray parenthetical statement from Section 2.2.3, “Installing Nexus Professional”. (NXBOOK-174)
- Minor rewording in Section 2.2.3, “Installing Nexus Professional”.
(NXBOOK-175) - Clarified that the note at the end of Section 2.3, “Upgrading Nexus” only applies when upgrading
from Nexus 1.2 to Nexus 1.3. (NXBOOK-179) -
Fixed a typo in Section 9.7.2, “Configuring Nexus Maven Plugin for Staging”:
Parameter incorrectly listed as "nexusURL" changed to "nexusUrl".
(NXBOOK-51)
Written by Tim OBrien
Tim is a Software Architect with experience in all aspects of software development from project inception to developing scaleable production architectures for large-scale systems during critical, high-risk events such as Black Friday. He has helped many organizations ranging from small startups to Fortune 100 companies take a more strategic approach to adopting and evaluating technology and managing the risks associated with change.
Explore All Posts by Tim OBrien