title: Is there better way of configuring repositories in Nexus?
body: <p>I have Nexus server, and maven user setting shared within team, that contains</p>
  
  <pre><code>  &lt;mirrors&gt;
        &lt;mirror&gt;
        &lt;!--This sends everything else to /public 
        http://www.sonatype.com/books/nexus-book/reference/maven-sect-single-group.html
        --&gt;
        &lt;id&gt;nexus&lt;/id&gt;
        &lt;mirrorOf&gt;*&lt;/mirrorOf&gt;
        &lt;url&gt;http://192.168.16.232:8081/nexus/content/groups/public&lt;/url&gt;
      &lt;/mirror&gt;    
    &lt;/mirrors&gt;
  </code></pre>
  
  <p>That is all repositories defined in pom.xml (including default Maven Central) are served by Nexus.</p>
  
  <p>In Nexus new repositories are added into public group.</p>
  
  <p><img src="https://i.stack.imgur.com/Eec9t.png" alt="Nexus public group"></p>
  
  <p>QUESTION: Is there better way? Currently other developers don't understand Nexus+Maven interaction and when there's new repository defined in pom.xml (that is not proxied by Nexus), maven will just say 'unable to get artifact'. But not "configure your Nexus server" :)
  Secondly I found that some public repository also cache from some others, so in the end, I can't be sure where exactly this jar came from.</p>
  
  <p>UPDATE: I am searching for the most beautiful, simple, easy to explain and understand solution.</p>