I’m getting desperate with this Problem: I want to export/run my Android Application with one additional .jar I added to the buildpath. I’m sure I added it correctly, there are 5 other .jars included and they all work fine.
with this special one I get the mentioned error.
I’ve already tried everything that can be found in this question:
"Conversion to Dalvik format failed with error 1" on external JAR
and several other links google spat out. The main Problem is, I actually do not understand what the message I appended want’s to tell me because if I add all the jars to a "normal" javaproject, it runs perfectly fine…
Developing on Android 4.0.3,
proguard 4.8,
adt 16.0.1.v201112150204-238534,
eclipse 3.7.1.r37
please help me
[2012-07-18 10:45:48 – myapp] Dx warning: Ignoring InnerClasses attribute for an anonymous inner
class (iaik.xml.crypto.XSecProvider$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 indicate that it is not an inner
class.…
…[2012-07-18 10:45:48 – myapp] Dx warning: Ignoring InnerClasses attribute for an anonymous inner
class (iaik.xml.crypto.XSecProvider$2) 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 indicate that it is not an inner
class.Ill-advised or mistaken usage of a core class (java.* or javax.*) when
not building a core library.This is often due to inadvertently including a core library file in
your application’s project, when using an IDE (such as Eclipse). If
you are sure you’re not intentionally defining a core class, then this
is the most likely explanation of what’s going on.However, you might actually be trying to define a class in a core
namespace, the source of which you may have taken, for example, from a
non-Android virtual machine project. This will most assuredly not
work. At a minimum, it jeopardizes the compatibility of your app with
future versions of the platform. It is also often of questionable
legality.If you really intend to build a core library — which is only
appropriate as part of creating a full virtual machine distribution,
as opposed to compiling an application — then use the
"–core-library" option to suppress this error message.If you go ahead and use "–core-library" but are in fact building an
application, then be forewarned that your application will still fail
to build or run, at some point. Please be prepared for angry customers
who find, for example, that your application ceases to function once
they upgrade their operating system. You will be to blame for this
problem.If you are legitimately using some code that happens to be in a core
package, then the easiest safe alternative you have is to repackage
that code. That is, move the classes in question into your own package
namespace. This means that they will never be in conflict with core
system classes. JarJar is a tool that may help you in this endeavor.
If you find that you cannot do this, then that is an indication that
the path you are on will ultimately lead to pain, suffering, grief,
and lamentation.[2012-07-18 10:45:48 – myapp] Dx 1 error; aborting
[2012-07-18 10:45:48 – myapp] Conversion to Dalvik format
failed with error 1
This is how my project looks int he explorer:
The problem is that the jar you are including has a class in the java.* or javax.* namespace. dx does not allow this, as mentioned in the last big error message.
If you actually need these classes, you’ll need to move them to a different package, using something like the jarjar tool. Otherwise, you’ll need to remove them from the jar — it may be possible to have proguard to remove them before everything gets dx’d, I’m not sure.