I. Problems and analysis
When doing an Android project, it is unavoidable to import the ready-made code directly into the Eclipse project. However, normal code often appears during the import process, and now even the import package will be faulted, as in the following scenario:
After the tree of normal items and unhealthy items,
Tree of unhealthy items: Tree of normal items:
A normal project has a Android2.2 package that is more than a normal project.
Second, the solution
Android Right-click Build path---Configure build path, select Android in the sidebar, select a project Build Target, which is the corresponding missing file. When selected, click Apply in the lower right corner and the project returns to normal.
three, the cause of the problem and its impactafter finding the relevant information, it was found that the eclipse development environment did not match during the project import process due to inconsistent JDK versions, resulting in the above error. In the Android project import process, after encountering the endless problems, such as: R file loss, jar packet loss, etc., these are not personal technical issues, is caused by the Eclipse development environment, but if the problem is not resolved often affect the normal continuation of the project. Each encounter problems similar are not exactly the same, after careful analysis of the problem, according to the location of the error check code, patience on the Internet to find relevant information, the problem is not difficult to solve.
Android Project Import Error---SOFTWARETESTINGHOMEWORK1