Proximity Configuration

This Guide is work in progress.

Proximity is made up from the following components:

  • Proximity - handles one or more repository. The order of the configured repositories is important.
  • Repository - may have storage and remote peer defined. It have also pluggable logic to orhestrate the retrieval See Repository Configuration.
  • ProximityLogic - orchestrates the inter-repository retrieval (like aggregation).
  • Indexer - used for fast searches only, not used in basic functionality.
  • AccessManager - decides whether to allow or forbid access (on Proximity or per repository level).
  • StatisticsGatherer - Service component, simply collects usage stats and serves them to Proximity.
These components makes the Proximity itself.

Architecture at glance

The Proximity simplified arhitecture is shown on this image:
An example of Proximity configuration: two proxied repositories, one for "central" (http://repo1.maven.org/maven2) and one for "apache.snapshot" (http://people.apache.org/maven-snapshot-repository/). Three inhouse (hosted) repositories for inhouse development. Developing Maven plugins but also inhouse projects. A fictive Maven + Proximity session, starts with a simple command line invocation like:




A simple request

TODO: "Who serves first - wins".

An aggregated request

TODO: "Who serves first - wins" + group search and aggregation.