[問題] Apache Tika library

看板AndroidDev作者Killercat (殺人貓™)時間13年前 (2011/05/21 00:18)推噓2(2推 0噓 7→)

留言9則, 2人參與討論串1/1

目前手邊有一個專案要用到Apache Tika來解析一些文件 http://tika.apache.org/ Android內涵了一些Apache的library 不過似乎不包含Tika 硬把這個Tika轉換成dex會出現以下的錯誤(如附件) 而在java底下是ok的我稍微看了一下javax/xml/stream/EventFilter.class這個東西不過也看不出個所以然有人有成功在Android下使用過tika嗎? -- [2011-05-20 16:35:54 - test2] Dx warning: Ignoring InnerClasses attribute for an anonymous inner class (com.sun.syndication.feed.impl.ToStringBean$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. [2011-05-20 16:35:55 - test2] Dx trouble processing "javax/xml/stream/EventFilter.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. [2011-05-20 16:35:55 - test2] Dx 1 error; aborting [2011-05-20 16:35:55 - test2] Conversion to Dalvik format failed with error 1 -- ※ 發信站: 批踢踢實業坊(ptt.cc) ◆ From: 114.43.127.159