title: SBT: adding the resolvers of a sbt project to those of the project depending on it
body: <p>I have a SBT project <code>A</code> published at <code>../nexus-url/.../a</code></p>
  
  <p>I have another SBT project <code>B</code> which depends on <code>A</code> and in order to acquire it, it adds <code>../nexus-url/.../a</code> to its list of resolvers. project <code>B</code> is published to <code>../nexus-url/.../b</code></p>
  
  <p>I have another SBT project <code>C</code> which depends on <code>B</code> and so in order to acquire it, it adds <code>../nexus-url/.../b</code> to its list of resolvers. </p>
  
  <p>Now, problem is that project <code>C</code> fails to add <code>B</code> as a dependency because it doesn't manage to find project <code>A</code>. I would have imagined that when importing <code>B</code>, it would look for its dependencies in <code>B</code>'s resolvers, but that doesn't seem to be happening. Was I wrong to expect this? </p>
  
  <p>If yes, Is there a way of embeding the <code>B</code>'s dependency information in the published package so that A can happily come along and import it?</p>