gradle

warning: Ignoring InnerClasses attribute for an anonymous inner class
(org.apache.xmlbeans.impl.tool.SchemaCodeGenerator$1) that doesn't come with an
associated EnclosingMethod attribute. This class was probably produced by a
compiler that did not target the modern .class file format. The recommended
solution is to recompile the class from source, using an up-to-date compiler
and without specifying any "-target" type options. The consequence of ignoring
this warning is that reflective operations on this class will incorrectly
warning: Ignoring InnerClasses attribute for an anonymous inner class
indicate that it is *not* an inner class.
(com.bea.xml.stream.util.CircularQueue$1) that doesn't come with an
this warning is that reflective operations on this class will incorrectly
going on.
This is often due to inadvertently including a core library file
building an application, then be forewarned that your application
Eclipse). If you are sure you're not intentionally defining a
core class, then this is the most likely explanation of what's
distribution, as opposed to compiling an application -- then use
conflict with core system classes. JarJar is a tool that may help
when not building a core library.
in your application's project, when using an IDE (such as
associated EnclosingMethod attribute. This class was probably produced by a
prepared for angry customers who find, for example, that your
your own package namespace. This means that they will never be in
will still fail to build or run, at some point. Please be
application ceases to function once they upgrade their operating
from a non-Android virtual machine project. This will most
system. You will be to blame for this problem.
solution is to recompile the class from source, using an up-to-date compiler
that is an indication that the path you are on will ultimately
core package, then the easiest safe alternative you have is to
lead to pain, suffering, grief, and lamentation.
assuredly not work. At a minimum, it jeopardizes the
and without specifying any "-target" type options. The consequence of ignoring
Ill-advised or mistaken usage of a core class (java.* or javax.*)
However, you might actually be trying to define a class in a core
It is also often of questionable legality.
repackage that code. That is, move the classes in question into
If you really intend to build a core library -- which is only
namespace, the source of which you may have taken, for example,
indicate that it is *not* an inner class.
trouble processing "javax/xml/XMLConstants.class":
If you are legitimately using some code that happens to be in a
If you go ahead and use "--core-library" but are in fact
compatibility of your app with future versions of the platform.
you in this endeavor. If you find that you cannot do this, then
appropriate as part of creating a full virtual machine
the "--core-library" option to suppress this error message.
compiler that did not target the modern .class file format. The recommended