sonatype / nexus-book Goto Github PK

The procurement chapter needs to be updated for latest versions of Nexus (at least 2.3.1, I couldn't check older versions)

The right-click menu doesn't offer anymore to approve or deny a group of artifacts but to set a rule for the right-clicked element. The dialog allows to set two kind of rules: approval/denial or requirement of a signature validation for the procured elements.

Section 3.7.1

Item 5 states
Change the owner and group of your Nexus-related directories, including nexus-work configured in nexus.properties defaulting to sonatype-work/nexus, to the nexus user that will run the application.

What is 'Nexus-related directories'? Is this overall just meaning the full installation tree that we untarred earlier? Just logs direectory? Since the only related directories are the install and the sonatype-work (I think), the wording would just be clearer to state that.

Some rulesets of Nexus Pro v2.11.4 are not described:

• "No promote action allowed"
• "No release action allowed"
• "Profile target matcher"

Nexus generates the prefixes.txt file for a hosted repository and makes it available for remote downloads. Each deployment of a new component will trigger an update of the file for the hosted repository as well as the prefix files for any repoisitory groups that contain the hosted repository.

repoisitory -> repository

There are multiple repeated words in the asciidoc files. Use the regex \b(\w+)\s+\1\b to find the typos.

Section 3.7.1

4.c states
Change PIDDIR to a directory where this user has read/write permissions. In most Linux distributions, /var/run is only writable by root. The property you need to add to customize the PID file location is wrapper.pid. For more information about this property and how it would be configured in wrapper.conf, see: http://wrapper.tanukisoftware.com/doc/english/properties.html.

So, do I just need to change the PIDDIR setting that is existing in the nexus script header, or do I additionally need to add this wrapper.pid? Going to the linked tanuki pages is confusing because the property there is documented as wrapper.pidfile since updated in a later version to be java.wrapper.pidfile.

I'm thinking I should only need to change PIDDIR, Grepping the script it appears that the tanuki property is handled internally and I should not care about it.

bash-4.1$ grep PID nexus
PIDDIR=/tmp
if [ "X$PIDDIR" = "X" ]
PIDDIR="bin/jsw/$DIST_OS-$DIST_ARCH-$DIST_BITS"
FIRST_CHAR=echo $PIDDIR | cut -c1,1
PIDDIR=$NEXUS_HOME/$PIDDIR
ANCHORFILE="$PIDDIR/$APP_NAME.anchor"
PIDFILE="$PIDDIR/$APP_NAME.pid"
if [ -f "$PIDFILE" ]
if [ -r "$PIDFILE" ]
pid=cat "$PIDFILE"
rm -f "$PIDFILE"
echo "Removed stale pid file: $PIDFILE"
echo "Cannot read $PIDFILE."
rm -f "$PIDFILE"
COMMAND_LINE="$CMDNICE "$WRAPPER_CMD" "$WRAPPER_CONF" wrapper.syslog.ident=$APP_NAME wrapper.pidfile="$PIDFILE" $ANCHORPROP $LOCKPROP"
COMMAND_LINE="$CMDNICE "$WRAPPER_CMD" "$WRAPPER_CONF" wrapper.syslog.ident=$APP_NAME wrapper.pidfile="$PIDFILE" wrapper.daemonize=TRUE $ANCHORPROP $IGNOREPROP $LOCKPROP"

Section 3.3

The line in the example of
$ ln -s nexus-2.9.0-02 nexus

Should read
$ sudo ln -s nexus-2.9.0-02 nexus

as the earlier cp and tar commands also required sudo to access /usr/local

Following the NPM repository instructions to create a new NPM Proxy repository, it wasn't clear that a restart was required otherwise the following error would occur when using the repository:

400 - Schema com.bolyuba.nexus.plugin.npm.service.PackageRoot has no registered handler!

In wrapper logs it looked like the NPM plugin wasn't installed / enabled until after the restart, so it's probably only needed the first time any NPM repository type is created. It may also affect other repository types.

Ideally Nexus wouldn't need a restart, but in the meantime could the documentation be updated to reflect the possible need for a restart?

Using Nexus 2.11

In the docs for 2.11 the section on migrating from Artifactory (chapter 'Migrating to Nexus') has been removed. I can't find any commit message explaining the logic behind this so it's probably a mistake. Please re-implement this!

https://github.com/sonatype/nexus-book/blob/master/chapter-smartproxy.asciidoc

The figures are not in the folder that they're suppose to be in.

TOC link is correct to 3.0/reference/sites.html but nav has 3.0/reference/site.html which is a 404.

In section 6.13, the book says:
"Nexus has three types of privileges:"

It lists the following:

• application privileges
• repository target privileges

The third is omitted or the number of privilege types is 2. Please advise.

The docs for the "POM must not contain release repository" ruleset is incorrect I think. It says that no repository element is allowed, but the ruleset name indicates that no release repository is allowed (allowing snapshot repositories).

404 Not Found - nginx/1.15.12: http://books.sonatype.com/nexus-book/index.html

groovy script for creating a new ldap connection for NEXUS OSS 3.x.x

The sentence following sentence has a typo: double dots at the end.

A typical, useful example would be to group the proxy repository that proxies the NuGet Gallery, a NuGet, hosted repository with internal software packages and another NuGet, hosted repository with third-party packages..