Fix Version/s: 2.1
@@ -17,9 +17,9 @@
1.4.6. Deploy 3rd Party Artifacts
How do you deal with that one-off JAR from a vendor that is not open source, and not available on
the Central Maven repository? You need to deploy these artifacts to a repository and configure your
-Maven instance to read from that repository. Instead of hand-crafting some POMs, download Nexus
+Maven instance to read from that repository. Instead of handcrafting some POMs, download Nexus
and take the two or three minutes it is going to take to get your hands on a tool that can create such
-a repository from 3rd-party artifacts. Nexus provides an intuitive upload form which you can use to
+a repository from 3rd-party artifacts. Nexus provides an intuitive upload form that you can use to
upload any random free-floating JAR that finds its way into your projects dependencies.
1.4.7. Collaborate with Internal Repositories
@@ -29,7 +29,7 @@
For example, consider a company that has 30 developers split into three groups of 10, each group focused
on a different part of the system. Without an easy way to share internal dependencies, a group like this
-is forced either to create an ad hoc filesystem-based repository or to build the system in its entirety so
+is forced either to create an ad-hoc filesystem-based repository or to build the system in its entirety so
that dependencies are installed in every developers local repository.
The alternative is to separate the projects into different modules that all have dependencies on artifacts
@@ -39,8 +39,3 @@
within the organization can deploy snapshots and artifacts to a local Nexus instance, and each group can
maintain a project structure which includes only the projects it is responsible for.