import-summary.txt 2.9 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273
  1. ECLIPSE ANDROID PROJECT IMPORT SUMMARY
  2. ======================================
  3. Manifest Merging:
  4. -----------------
  5. Your project uses libraries that provide manifests, and your Eclipse
  6. project did not explicitly turn on manifest merging. In Android Gradle
  7. projects, manifests are always merged (meaning that contents from your
  8. libraries' manifests will be merged into the app manifest. If you had
  9. manually copied contents from library manifests into your app manifest
  10. you may need to remove these for the app to build correctly.
  11. Ignored Files:
  12. --------------
  13. The following files were *not* copied into the new Gradle project; you
  14. should evaluate whether these are still needed in your project and if
  15. so manually move them:
  16. * ic_launcher-web.png
  17. * proguard-project.txt
  18. Replaced Jars with Dependencies:
  19. --------------------------------
  20. The importer recognized the following .jar files as third party
  21. libraries and replaced them with Gradle dependencies instead. This has
  22. the advantage that more explicit version information is known, and the
  23. libraries can be updated automatically. However, it is possible that
  24. the .jar file in your project was of an older version than the
  25. dependency we picked, which could render the project not compileable.
  26. You can disable the jar replacement in the import wizard and try again:
  27. android-support-v4.jar => com.android.support:support-v4:22.2.1
  28. android-support-v7-appcompat.jar => com.android.support:appcompat-v7:22.2.1
  29. Replaced Libraries with Dependencies:
  30. -------------------------------------
  31. The importer recognized the following library projects as third party
  32. libraries and replaced them with Gradle dependencies instead. This has
  33. the advantage that more explicit version information is known, and the
  34. libraries can be updated automatically. However, it is possible that
  35. the source files in your project were of an older version than the
  36. dependency we picked, which could render the project not compileable.
  37. You can disable the library replacement in the import wizard and try
  38. again:
  39. android-support-v7-appcompat => [com.android.support:appcompat-v7:22.2.1]
  40. google-play-services_lib => [com.google.android.gms:play-services:+]
  41. Moved Files:
  42. ------------
  43. Android Gradle projects use a different directory structure than ADT
  44. Eclipse projects. Here's how the projects were restructured:
  45. * AndroidManifest.xml => app/src/main/AndroidManifest.xml
  46. * assets/ => app/src/main/assets
  47. * lint.xml => app/lint.xml
  48. * res/ => app/src/main/res/
  49. * src/ => app/src/main/java/
  50. Next Steps:
  51. -----------
  52. You can now build the project. The Gradle project needs network
  53. connectivity to download dependencies.
  54. Bugs:
  55. -----
  56. If for some reason your project does not build, and you determine that
  57. it is due to a bug or limitation of the Eclipse to Gradle importer,
  58. please file a bug at http://b.android.com with category
  59. Component-Tools.
  60. (This import summary is for your information only, and can be deleted
  61. after import once you are satisfied with the results.)