title: Does it really matter if the project library I use has a different minSdkVersion and targetSdkVersion from my main project
body: <p>Currently, my main project is having the following configuration</p>
  
  <pre><code>&lt;uses-sdk
      android:minSdkVersion="10"
      android:targetSdkVersion="16" /&gt;
  </code></pre>
  
  <p>I'm using ActionbarSherlock, Google Play services and Sliding menu libraries too. They are having different configuration.</p>
  
  <h2>ActionbarSherlock</h2>
  
  <pre><code>&lt;uses-sdk android:minSdkVersion="7" android:targetSdkVersion="16"/&gt;
  </code></pre>
  
  <h2>Google Play services</h2>
  
  <pre><code>&lt;uses-sdk android:minSdkVersion="8"/&gt;  
  </code></pre>
  
  <h2>Sliding menu</h2>
  
  <pre><code>&lt;uses-sdk
      android:minSdkVersion="5"
      android:targetSdkVersion="17" /&gt;
  </code></pre>
  
  <p>I was wondering, is there any side effect, of letting my library projects having different different minSdkVersion and targetSdkVersion? So far my testing is they work without problem. However, I might be missing out something else.</p>
  
  <p>Also, what about case, of having one of the libraries, to have higher target SDK version than main project?</p>