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



      @@ -7,7 +7,7 @@

      third party dependency to intense scrutiny and testing before making an artifact available to build a
      release or support a team of developers. In most Enterprise development environments, a developer can't
      just decide to add in a new dependency to Hibernate or to the Spring Framework on a whim; the decision
      -to add dependencies to third-party libraries will need to be funnelled through an oversight process that
      +to add dependencies to third-party libraries will need to be funneled through an oversight process that
      relies on an architect or an administrator to promote artifacts to a certified release repository.

      Another, more common experience is an organization which needs to proxy something like the Central
      @@ -37,8 +37,3 @@

      not change if the third-party, external proxied repository does. This is an extra level of assurance that
      your release artifacts depend on a set of artifacts under your complete control.


        There are no comments yet on this issue.


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


            • Created: