Conversion to Dalvik format failed with error 1【提示翻译】

提示信息：

[2013-09-28 09:18:59 - WeiZhiC] Dx 1 error; aborting
[2013-09-28 09:18:59 - WeiZhiC] Conversion to Dalvik format failed with error 1
trouble processing "java/sql/Savepoint.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).
当使用IDE（例如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.
然而，也许你缺失想要创建一个类在核心命名空间，你所引用的资源，例如，从一个非Android vm工程中。这将特别确定地不会起作用。
在最低版本，他会危害你的应用向上兼容。

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.
如果你真的试图创建一个内核库 -- 仅仅是占有一个完整vm的一部分，而不是编译这个app -- 那么使用“core-library”选项去阻止错误信息出现。

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.
如果你继续使用“core-library”，但事实上是构建一个app，那么提前警告，在某一时刻，你的app仍然会构建或运行失败。
请准备好面对发现这个错误的顾客，例如，你的app 实例停止运行，一旦他们更新升级他们的系统。你将受到责备。

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.。
如果你恰巧合理地使用一些在内核包中的代码，那么你所有的最简单的安全选择是重新打包那段代码。
也就是说，将这些类移动到你自己命名的包中去。这样意味着这些类将永远不会和内核系统类发生冲突。
JarJar是个工具可以帮助你在这努力。如果你发现自己不能这样做，那么也就指示着，你将走上一条痛苦...的道路。

 

我的解决办法：Configure Buld Path中，并没有自定义的核心库，我也没有写什么核心类。但是在Liabraries的根文件夹下多了androi.jar,而android.jar应该出现在在android.4.2.2包下。删除多余的包，clean 工程。

【好奇怪的错误，昨天没问题，今天Eclipse启动就有了】