title: Why version of SBT is playing role in name of fully qualified dependency?
body: <p>Why version of SBT is playing role in name of fully qualified dependency ?</p>
  
  <p>I thought it only depends on version of Scala.</p>
  
  <p>Here is example.</p>
  
  <ul>
  <li><code>build.sbt</code> has <code>scalaVersion</code> set to <code>2.10.2</code></li>
  <li><code>build.properties</code> has <code>sbt.version</code> set to <code>0.12.1</code></li>
  <li><code>plugins.sbt</code> has plugin dependency <code>"com.github.siasia" %% "xsbt-web-plugin" % "0.12.0-0.2.11.1"</code></li>
  </ul>
  
  <p>If I build it I see following in the log:</p>
  
  <pre><code>[info] Resolving com.github.siasia#xsbt-web-plugin_2.9.2;0.12.0-0.2.11.1 ...
  </code></pre>
  
  <p>But if I change <code>sbt.version</code> set to <code>0.13.0-RC5</code> SBT fails to find this plugin and says in the log</p>
  
  <pre><code>[info] Resolving com.github.siasia#xsbt-web-plugin_2.10;0.12.0-0.2.11.1 ...
  </code></pre>
  
  <p>Why did it change scala version if it remains 2.10.2 in my config ? How to fix it ?</p>