Advertisement
Guest User

gradle build failed

a guest
Oct 19th, 2015
493
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 5.15 KB | None | 0 0
  1. Information:Gradle tasks [:app:generateDebugSources, :app:generateDebugAndroidTestSources, :app:assembleDebug]
  2. :app:preBuild UP-TO-DATE
  3. :app:preDebugBuild UP-TO-DATE
  4. :app:checkDebugManifest
  5. :app:preReleaseBuild UP-TO-DATE
  6. :app:prepareComAndroidSupportAppcompatV72310Library UP-TO-DATE
  7. :app:prepareComAndroidSupportMultidex101Library UP-TO-DATE
  8. :app:prepareComAndroidSupportSupportV42310Library UP-TO-DATE
  9. :app:prepareDebugDependencies
  10. :app:compileDebugAidl UP-TO-DATE
  11. :app:compileDebugRenderscript UP-TO-DATE
  12. :app:generateDebugBuildConfig UP-TO-DATE
  13. :app:generateDebugAssets UP-TO-DATE
  14. :app:mergeDebugAssets UP-TO-DATE
  15. :app:generateDebugResValues UP-TO-DATE
  16. :app:generateDebugResources UP-TO-DATE
  17. :app:mergeDebugResources UP-TO-DATE
  18. :app:processDebugManifest UP-TO-DATE
  19. :app:processDebugResources UP-TO-DATE
  20. :app:generateDebugSources UP-TO-DATE
  21. :app:preDebugAndroidTestBuild UP-TO-DATE
  22. :app:prepareDebugAndroidTestDependencies
  23. :app:compileDebugAndroidTestAidl UP-TO-DATE
  24. :app:processDebugAndroidTestManifest UP-TO-DATE
  25. :app:compileDebugAndroidTestRenderscript UP-TO-DATE
  26. :app:generateDebugAndroidTestBuildConfig UP-TO-DATE
  27. :app:generateDebugAndroidTestAssets UP-TO-DATE
  28. :app:mergeDebugAndroidTestAssets UP-TO-DATE
  29. :app:generateDebugAndroidTestResValues UP-TO-DATE
  30. :app:generateDebugAndroidTestResources UP-TO-DATE
  31. :app:mergeDebugAndroidTestResources UP-TO-DATE
  32. :app:processDebugAndroidTestResources UP-TO-DATE
  33. :app:generateDebugAndroidTestSources UP-TO-DATE
  34. :app:processDebugJavaRes UP-TO-DATE
  35. :app:compileDebugJavaWithJavac UP-TO-DATE
  36. :app:compileDebugNdk UP-TO-DATE
  37. :app:compileDebugSources UP-TO-DATE
  38. :app:collectDebugMultiDexComponents UP-TO-DATE
  39. :app:packageAllDebugClassesForMultiDex
  40. :app:shrinkDebugMultiDexComponents
  41. :app:createDebugMainDexClassList
  42. :app:dexDebug
  43. warning: Ignoring InnerClasses attribute for an anonymous inner class
  44. (org.apache.xmlbeans.impl.tool.SchemaCodeGenerator$1) that doesn't come with an
  45. associated EnclosingMethod attribute. This class was probably produced by a
  46. compiler that did not target the modern .class file format. The recommended
  47. solution is to recompile the class from source, using an up-to-date compiler
  48. and without specifying any "-target" type options. The consequence of ignoring
  49. this warning is that reflective operations on this class will incorrectly
  50. indicate that it is *not* an inner class.
  51. warning: Ignoring InnerClasses attribute for an anonymous inner class
  52. (com.bea.xml.stream.util.CircularQueue$1) that doesn't come with an
  53. associated EnclosingMethod attribute. This class was probably produced by a
  54. compiler that did not target the modern .class file format. The recommended
  55. solution is to recompile the class from source, using an up-to-date compiler
  56. and without specifying any "-target" type options. The consequence of ignoring
  57. this warning is that reflective operations on this class will incorrectly
  58. indicate that it is *not* an inner class.
  59. trouble processing "javax/xml/XMLConstants.class":
  60. Ill-advised or mistaken usage of a core class (java.* or javax.*)
  61. when not building a core library.
  62. This is often due to inadvertently including a core library file
  63. in your application's project, when using an IDE (such as
  64. Eclipse). If you are sure you're not intentionally defining a
  65. core class, then this is the most likely explanation of what's
  66. going on.
  67. However, you might actually be trying to define a class in a core
  68. namespace, the source of which you may have taken, for example,
  69. from a non-Android virtual machine project. This will most
  70. assuredly not work. At a minimum, it jeopardizes the
  71. compatibility of your app with future versions of the platform.
  72. It is also often of questionable legality.
  73. If you really intend to build a core library -- which is only
  74. appropriate as part of creating a full virtual machine
  75. distribution, as opposed to compiling an application -- then use
  76. the "--core-library" option to suppress this error message.
  77. If you go ahead and use "--core-library" but are in fact
  78. building an application, then be forewarned that your application
  79. will still fail to build or run, at some point. Please be
  80. prepared for angry customers who find, for example, that your
  81. application ceases to function once they upgrade their operating
  82. system. You will be to blame for this problem.
  83. If you are legitimately using some code that happens to be in a
  84. core package, then the easiest safe alternative you have is to
  85. repackage that code. That is, move the classes in question into
  86. your own package namespace. This means that they will never be in
  87. conflict with core system classes. JarJar is a tool that may help
  88. you in this endeavor. If you find that you cannot do this, then
  89. that is an indication that the path you are on will ultimately
  90. lead to pain, suffering, grief, and lamentation.
  91. 1 error; aborting
  92. Error:Execution failed for task ':app:dexDebug'.
  93. > com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException: Process 'command 'C:\Program Files\Java\jdk1.7.0_79\bin\java.exe'' finished with non-zero exit value 1
  94. Information:BUILD FAILED
  95. Information:Total time: 40.083 secs
  96. Information:1 error
  97. Information:0 warnings
  98. Information:See complete output in console
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement