EclipseADTClassPathFile.md

##Without the compatibility library

##With the compatibility library

##.classpath file

Classpath file remains the same. Adding / removing the compatability library doesn't change that.

<?xml version="1.0" encoding="UTF-8"?>
<classpath>
  <classpathentry kind="src" path="gen"/>
	<classpathentry kind="con" path="com.android.ide.eclipse.adt.ANDROID_FRAMEWORK"/>
	<classpathentry exported="true" kind="con" path="com.android.ide.eclipse.adt.LIBRARIES"/>
	<classpathentry exported="true" kind="con" path="com.android.ide.eclipse.adt.DEPENDENCIES"/>
	<classpathentry kind="src" output="bin/classes" path="src">
		<attributes>
			<attribute name="maven.pomderived" value="true"/>
		</attributes>
	</classpathentry>
	<classpathentry exported="true" kind="con" path="org.eclipse.m2e.MAVEN2_CLASSPATH_CONTAINER">
		<attributes>
			<attribute name="maven.pomderived" value="true"/>
		</attributes>
	</classpathentry>
	<classpathentry kind="output" path="bin/classes"/>
</classpath>

Android Libraries classpath container

The granularity of the classpath is set on the container level. (cfr Android Private Libraries). We can remove that from the .classpath file, but it will remove the entire container (as can be seen in the screenshot below).

<classpathentry exported="true" kind="con" path="com.android.ide.eclipse.adt.LIBRARIES"/>