Eclipse: Why And When To Add Libraries To Build Path When Using Maven Project To Not Have Defective Eclipse Project?

I have an Android project in Eclipse managed by Maven. Yesterday I upgraded Eclipse and some plugins by the 'Checked for Updated' function within Eclipse. After the update has fini

Solution 1:

As of version 1.0.0 Android for Maven Eclipse has changed the way it manages the Maven classpaths. Non-runtime dependencies (effectively, anything not in the compile scope) are now loaded into a new Maven, non-runtime classpath container. Are you seeing these libraries appear in this new classpath container?

If not, please try deleting the project from your workspace, deleting the IDE-specific .* metadata files and trying re-importing as a Maven project.