Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Fix Version/s: 2.1

      Description

      +++

      @@ -1,4 +1,4 @@

      -components or dependencies are referred to as artifacts, a term which can refer to any generic software
      +components or dependencies are referred to as "artifacts", a term which can refer to any generic software
      artifact including components, libraries, frameworks, containers, etc. Maven can identify artifacts in
      repositories, understand their dependencies, retrieve all that are needed for a successful build, and deploy
      its output back to repositories when done.
      @@ -7,8 +7,8 @@

      dependencies in Maven Central. If they happen to use another remote repository or if they need to add a
      custom artifact, the solution, in Stage Zero, is to manually manipulate the files in a local repository and
      share this local repository with multiple developers. While this approach may yield a working build for
      -a small team, managing a shared local repository doesnt allow an organization to scale a development
      -effort; there is no inherent control over who can set up a local repository, who can add to them or change
      +a small team, managing a shared local repository doesn't allow an organization to scale a development
      +effort. There is no inherent control over who can set up a local repository, who can add to them or change
      or delete from them, nor are there tools to protect the integrity of these repositories.

      That is, until Repository Managers were introduced.
      @@ -25,9 +25,9 @@

      artifacts can be downloaded once and stored locally. After Stage One, your builds run considerably
      faster than they did when you relied upon the Central Maven repository.

      -Once youve installed Nexus and youve configured all of your organizations clients to use it as a
      +Once you've installed Nexus and you've configured all of your organization's clients to use it as a
      single point of access to remote repositories, you begin to realize that it now provides you with a central
      -configuration point for the artifacts used throughout your organization. Once youve started to proxy,
      +configuration point for the artifacts used throughout your organization. Once you've started to proxy,
      you can start to think about using Nexus as a tool to control policy and what dependencies are allowed
      to be used in your organization. Nexus Professional provides a procurement plugin which allows for
      finegrained control over which artifacts can be accessed from a remote repository. This procurement
      @@ -35,13 +35,9 @@

      1.5.3. Stage Two: Hosting a Repository Manager
      Once you have started to proxy remote repositories and you are using Nexus as a single, consolidated
      -access point for remote repositories. You can start to deploy your own artifacts to Nexus hosted
      +access point for remote repositories, you can start to deploy your own artifacts to Nexus hosted
      repositories. Most people approach repository management to find a solution for proxying remote
      repositories, and while proxying is the most obvious and immediate benefit of installing a repository
      manager, hosting internally generated artifacts tends to be the stage that has the most impact on
      collaboration within an organization.

        Activity

        Hide
        Tim O'Brien added a comment -

        Fixed

        Show
        Tim O'Brien added a comment - Fixed

          People

          • Assignee:
            Tim O'Brien
            Reporter:
            Tim O'Brien
            Last Updated By:
            Manfred Moser
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: