anchor.diff:  [[nexus-connecting-to-nexus]]
   == Connecting to Nexus
   
  -The next steps demonstrate defining a build that will use the new Nexus
  -repository.  The rest of the tutorial will be using
  -link:https://github.com/openshift/jee-ex.git[this example repository]
  -with *wildfly-100-centos7* as a builder, but these changes should work for any
  -project.
  +The next steps demonstrate defining a build that uses the new Nexus repository.
  +The rest of the tutorial uses link:https://github.com/openshift/jee-ex.git[this
  +example repository] with *wildfly-100-centos7* as a builder, but these changes
  +should work for any project.
   
  -The example builder image, *wildfly-100-centos7* supports `*MAVEN_MIRROR_URL*` as
  -part of its environment, so we can use this to point our builder image to our
  -Nexus repository. If your image does not support consuming an environment
  -variable to configure a Maven mirror, you may need to modify the builder image
  -to provide the correct Maven settings to point to the Nexus mirror.
  +The link:https://github.com/openshift/jee-ex.git[example builder image] supports
  +`*MAVEN_MIRROR_URL*` as part of its environment, so we can use this to point our
  +builder image to our Nexus repository. If your image does not support consuming
  +an environment variable to configure a Maven mirror, you may need to modify the
  +builder image to provide the correct Maven settings to point to the Nexus
  +mirror.
   
   ----
   $ oc new-build openshift/wildfly-100-centos7:latest~https://github.com/openshift/jee-ex.git \
  
positive.code: $ oc logs build/jee-ex-1 --follow
  ----
  
  Replace `<Nexus_Project>` with the project name of the Nexus repository.  If it
  is in the same project as the application that is using it, you can remove the
  `<Nexus_Project>.`.
  xref:../../architecture/additional_concepts/networking.adoc#architecture-additional-concepts-networking[Learn more about DNS resolution in {product-title}].
  
negative.code: [[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_*.
  
  [[nexus-additional-resources]]
  == Additional Resources
  * 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]
  