Want more features on Pastebin? Sign Up, it's FREE!
Guest

Android error

By: a guest on May 8th, 2012  |  syntax: None  |  size: 2.26 KB  |  views: 37  |  expires: Never
download  |  raw  |  embed  |  report abuse  |  print
Text below is selected. Please press Ctrl+C to copy to your clipboard. (⌘+C on Mac)
  1. [2012-05-08 23:59:33 - com.android.ide.eclipse.adt.internal.project.AndroidManifestHelper] Unable to read AndroidManifest.xml: org.eclipse.core.internal.resources.ResourceException: Resource is out of sync with the file system: 'AndroidManifest.xml'.
  2. AndroidManifest.xml does not declare a Java package: Build aborted.
  3. Dx
  4. trouble processing "javax/xml/bind/annotation/XmlAccessType.class":
  5.  
  6. Ill-advised or mistaken usage of a core class (java.* or javax.*)
  7. when not building a core library.
  8.  
  9. This is often due to inadvertently including a core library file
  10. in your application's project, when using an IDE (such as
  11. Eclipse). If you are sure you're not intentionally defining a
  12. core class, then this is the most likely explanation of what's
  13. going on.
  14.  
  15. However, you might actually be trying to define a class in a core
  16. namespace, the source of which you may have taken, for example,
  17. from a non-Android virtual machine project. This will most
  18. assuredly not work. At a minimum, it jeopardizes the
  19. compatibility of your app with future versions of the platform.
  20. It is also often of questionable legality.
  21.  
  22. If you really intend to build a core library -- which is only
  23. appropriate as part of creating a full virtual machine
  24. distribution, as opposed to compiling an application -- then use
  25. the "--core-library" option to suppress this error message.
  26.  
  27. If you go ahead and use "--core-library" but are in fact
  28. building an application, then be forewarned that your application
  29. will still fail to build or run, at some point. Please be
  30. prepared for angry customers who find, for example, that your
  31. application ceases to function once they upgrade their operating
  32. system. You will be to blame for this problem.
  33.  
  34. If you are legitimately using some code that happens to be in a
  35. core package, then the easiest safe alternative you have is to
  36. repackage that code. That is, move the classes in question into
  37. your own package namespace. This means that they will never be in
  38. conflict with core system classes. JarJar is a tool that may help
  39. you in this endeavor. If you find that you cannot do this, then
  40. that is an indication that the path you are on will ultimately
  41. lead to pain, suffering, grief, and lamentation.
  42.  
  43. Dx 1 error; aborting
  44. Conversion to Dalvik format failed with error 1
clone this paste RAW Paste Data