anchor.diff:  
   
     |Maven Metadata.xml repair
  -  
  +
     |&#10004;
  -  
  +
     |&#10004; +
     Not required. Artifactory's Maven metadata.xml is server calculated and is inherently up-to-date.
   
  
positive.code: |Report for Problem Artifacts
  |&#10004;
  |By default blocks bad poms in runtime instead of polluting your repository and reporting after the fact (policy is configurable via UI)
  |&#10004; + 
  RSS Feeds and UI viewer for bad checksums and artifacts with bad poms. 
  Bad poms are allowed through by default because many times Maven can still use them. We don't believe that simply inserting a repo manager should cause things to suddenly fail from Central. The repo man should for the most part be transparent by default
  
  |Repository Statistics
  |&#10004; + 
  Per repository or as a comparison among multiple repositories
  |&#10004; +  
  - Binaries Count +
  - Binaries Size +
  - Artifacts Size +
  
negative.code: http://www.jfrog.com/home/v_artifactorycloud_overview[Artifactory Online] - private Artifactory instance in the cloud with full self service, pay-per-use model and always up-to-date with all the latest features
  
  |&#10008;
  
  4+|*Artifacts and Metadata Storage*
  
  |Artifacts storage
  
  |Filesystem
  
  a| - Filesystem +
   - Database (not reccomeneded for large repositories), +
  