anchor.diff:  [[nexus-confirming-success]]
   == Confirming Success
   
  -In your web browser, navigate to
  -*_http://<Nexus IP>:8081/content/groups/public_* to confirm that it has stored
  -your application's dependencies. You can also check the build logs to see if
  -Maven is using the Nexus mirror. If successful, you should see output
  -referencing the URL *_http://nexus:8081_*.
  +In your web browser, navigate to *_http://<Nexus
  +IP>:8081/content/groups/public_* to confirm that it has stored your
  +application's dependencies. You can also check the build logs to see if Maven is
  +using the Nexus mirror. If successful, you should see output referencing the URL
  +*_http://nexus:8081_*.
   
   [[nexus-additional-resources]]
   == Additional Resources
  -* xref:../volumes.adoc#dev-guide-volumes[Managing Volumes in {product-title}]
  +* xref:../../dev_guide/volumes.adoc#dev-guide-volumes[Managing Volumes in {product-title}]
   * link:https://blog.openshift.com/improving-build-time-java-builds-openshift/[Improving Build Time of Java Builds on {product-title}]
   * link:https://books.sonatype.com/nexus-book/reference/index.html[Nexus Repository Documentation]
  
positive.code: ----
  
  This removes the previous *emptyDir* volume for the deployment config and adds a
  claim for 1 gigabyte of persistent storage mounted at `/sonatype-work`, which
  is where our dependencies will be stored. Due to the change in configuration,
  the Nexus pod will be redeployed automatically.
  
  Verify that Nexus is running by refreshing the Nexus page in your browser. You
  can monitor the deployment's progress using:
  
  ----
  $ oc get pods -w
  
negative.code: link:https://books.sonatype.com/nexus-book/reference/config.html[the Nexus documentation]
  to configure your build properly.
  
  Furthermore, make sure that you give each pod enough resources to function. You
  may have to
  xref:../../dev_guide/deployment#creating-a-deployment-configuration[edit the pod
  template] in the Nexus deployment configuration to request more resources.
  
  [[nexus-setting-up-nexus]]
  == Setting up Nexus
  
  . Download and deploy the official Nexus container image:
  +
  ----
  oc new-app sonatype/nexus
  ----
  
  . Create a route by exposing the newly created Nexus service:
  +
  ----
  oc expose svc/nexus
  ----
  
  . Use *oc get routes* to find the pod's new external address.
  +
  ----
  oc get routes
  ----
  +
  The output should resemble:
  +
  ----
  NAME      HOST/PORT                              PATH      SERVICES   PORT       TERMINATION
  nexus     nexus-myproject.192.168.1.173.xip.io             nexus      8081-tcp
  ----
  
  . Confirm that Nexus is running by navigating your browser to the URL under
  *HOST/PORT*. To sign in to Nexus, the default administrator username is *admin*,
  and the password is *admin123*.
  
  [NOTE]
  ====
  Nexus comes pre-configured for the Central Repository, but you may need others
  for your application. For many Red Hat images, it is recommended to link:https://books.sonatype.com/nexus-book/reference/config-maven.html[add the
  *jboss-ga* repository] at link:https://maven.repository.redhat.com/ga/[Maven repository].
  ====
  
  [[nexus-using-probes-to-check-for-success]]
  === Using Probes to Check for Success
  
  This is a good time to set up
  xref:../../dev_guide/application_health.adoc#dev-guide-application-health[readiness
  and liveness probes]. These will periodically check to see that Nexus is running
  properly.
  
  ----
  $ oc set probe dc/nexus \
  