title: Adding Android library project to Eclipse build path?
body: <p>I have a multi module Android Maven project which consists of several projects and an Android library project (baselib) where I run non Android based JUnit tests. </p>
  
  <p><img src="https://i.stack.imgur.com/OVmz3.jpg" alt="enter image description here"></p>
  
  <p>This works as long as I run the test by Maven. When I run the baselib JUnit tests by Eclipse with Run->As JUnit test, I don't get the current version. That means that changes in the JUnit test have no effect until I make a Maven build.   </p>
  
  <p>I thought about adding the bin folder to the Eclipse build path, but I get an error message in Eclipse: </p>
  
  <blockquote>
    <p>Cannot nest output folder ...baselib-TRUNK/bin/classes inside
    ...baselib-TRUNK/bin</p>
  </blockquote>
  
  <p>That's somehow clear. So I thought about adding the jar itself to the build path. I added it once as external jar, then once as jar. But I still don't get the current version of the code although the timestamp of the jar has the current version if I modify and save some code. (Build Automatically is checked in Eclipse). Output folder is recognized by Eclipse's build path configuration as .../bin/classes which is set in pom.xml. I also tried to add <strong>/bin/test-classes</strong> to build path which contains the test class itself, but still no new version of the code.</p>
  
  <p>Why does this not work to get the current version and how can I solve this? </p>